Hi everyone! Does anyone know how to set up automation in Jira Software (Team-managed)?
The setup I’m aiming for is:
When the status of an Epic changes, it should automatically add a comment to a related Jira Service Management ticket or any linked work items.
Hi @Julina Del Rosario ,
Thank you for your question.
Like company-managed projects, the team-managed projects also have automation capability. Just go in project setting and Automation section.
The automation could be similiar to the following:
I hope it helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Julina Del Rosario
@Matteo Vecchiato's answer is incomplete.
The structure provide is mostly correct, but Matteo did not address your need to act against issues in a different project.
If the rule is built from the project settings of the JSW project, then the scope of the rule will be set to only that project.
When you want an automation to look at issues from multiple projects (the primary JSW project and linked issues in other projects) you need to make a rule that is Global or Multiple-Project Scoped. The rule will not be able to find or update the linked issues in other projects is the scope is set to only the JSW project.
Global and Multiple-Project Scoped rules can be created only by Jira Product Administrators and the creation can happen only from the Settings > System > Global Automations page.
Additionally, because the rule will be scoped for multiple (or all) projects you will need to add conditions to restrict the actions to projects of interest.
For example, the trigger will be triggered for transitions in EVERY project and EVERY issue type.
The example includes the condition to check that the triggering issue is an Epic, which is correct.
You need another condition to check that the triggering issue is in the JSW project of interest.
If you want to limit the issues to which you add comments to be issues in only certain projects, then you will need to add a condition in the branch to check that the found issues are in the target projects. Or set the scope to Multiple Projects and specify just the source JSW project and the target projects of interest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Trudy Claspill , thank you for giving more detail. As written in my post, the automation is similar and it was just to addressing to the solution, not to giving a complete solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.