Using Automation in Jira to add issue/"Work item" to an Epic
Automation for Jira
Request:
In some cases there are specific work items expected to be added to a specific epic. This could be based on a custom field value, label, component, etc. This article will show an example automation rule for achieving this.
In this case, users have already created an Epic, and the goal is to ensure that any newly created work item is automatically assigned to that Epic.
The solution lies in utilizing Automation for Jira.
First way:
-
To begin, we need to establish a trigger, which in this instance will involve creating a work item.
-
Ensure to include a condition that verifies whether the newly created work item is not classified as an Epic and that the Parent field is empty.
-
We then update the parent field of the work item to include an active Epic. Any new work item created will automatically be associated with the Epic specified in the parent field.
Second way:
Work items have already been created, and we have either added a component, a label, or a custom field of your choice. In this example, I have added a component.
Additionally, I created an Epic using Automation. The JQL query verifies that the issue type is an Epic, is open, and has an associated component.
Within the branch, I am executing a JQL query to retrieve any work items that share the same component as the Epic mentioned above.
Always validate your queries to ensure accuracy and relevance.
The final step involves editing the work items returned by the JQL and updating the parent field to reflect the Epic that initiated the Automation rule.
I hope you found this article enjoyable and insightful.
We would love to hear your thoughts, so please feel free to share your feedback!
Was this helpful?
Thanks!
Tinker Fadoua
3 comments