Initiative sets in canceled - also all tickets related get the same status

[Stefano De Santis]

I need a global automation that if I set the status "canceled" to an initiative then all the children, both work packages and epics and stories, take the status canceled

[Manoj Gangwar · Accepted solution]

Hi @Stefano De Santis 

You can create an automation like below example:

Example of Automation Rule Configuration:

• Trigger: Issue Transitioned

  • Status: Canceled

• Condition: Issue Fields Condition

  • Field: Issue Type
  • Condition: equals
  • Value: Initiative

• Action: Branch rule / related issues

  • Branch: Children

• Action within Branch: Edit Issue

  • Field: Status
  • Value: Canceled

[Trudy Claspill]

Adding to this...

@Stefano De Santis 

Do you use only Company Managed projects in your instance or do you also use Team Managed projects?

If you use Team Managed projects do you expect the issues in those projects to be transitioned also?

[Stefano De Santis]

I want to spread the rule also to Team Managed projects. Thank you

[Trudy Claspill]

I do not believe you can use a Global rule to change statuses on issues in Team Managed projects.

Within an Automation rule when you use a Transition Issue action and select a specific status, in the backend the automation rule is finding the unique ID associated with that Status.

Company Managed projects use globally defined status values, so the "Canceled" status in them is the same single Status in the backend.

Team Managed project have project specific statuses. Even if the Team Managed project uses a status named "Canceled" it is a different status the the "Canceled" status used in Company Managed projects and different from any "Canceled" status used in another Team Managed project. The backend ID for each of those Canceled statuses will be different. A Global automation rule won't be able to determine which one it should actually use.

You mentioned "initiatives" as the trigger issue.

Are you using a Premium or Enterprise subscription where you have extended the Issue Type Hierarchy to include level(s) above Epics for Initiative and potentially other issues? That would add another wrinkle to the use the creation of the rule(s) since the issue hierarchy can't be extended directly in Team Managed projects. Instead you have to have the issues for those additional levels in a Company Managed project, and make the TM issues children of those CM project issues.

I think that you would have to have multiple rules, with rules specifically for each Team Managed project.

[Stefano De Santis]

I use an Enterprise subscription

[Trudy Claspill]

Are you cross-project-parenting the issues so that Team Managed project issue might be descendants under Initiatives?