advanced plans - tracking status does not work out

[Verena Schwegel]

Hi all,

I do have a problem with the automatic updating of the tracking status in advanced plans. f.ex. "Phase" is "open" --> dedicated "Epics" already "in progress", but "Phase" is still "open". How can I solve this?

Thanks in advance!

BR

Verena

[Walter Buggenhout]

Hi @Verena Schwegel and welcome to the Community!

Maybe your expectations are a bit off here; although advanced roadmaps adds a lot of additional functionality to take planning, tracking and management to a level way beyond single projects, automated synchronisation of statuses is not one of them.

One thing you can do - not automated, but not a lot of work - is manually updating statuses of parent issues from the advanced roadmaps plan view. As the interface has a very spreadsheet-like look and feel, it is easy to display statuses of issues in hierarchy. And, when the status custom field is visible in the scope table, you can update statuses inline with very little effort. After reviewing your changes and saving the updates to Jira, the status update will be reflected there as well.

An automated option is available too. You can build automation rules to update the status of parent issues when the status of a child issue is changed. I added links to 2 template rules from the template library to get you started:

• Change the status of an Epic when the status of one or all of its linked issues changes 
• Close parent when all sub-tasks have been completed 

Hope this helps!

[Verena Schwegel]

Hi Walter,

thanks for your feedback. I already defined automation rules, but it still does not work out. Now I will check the links you sent me. Thanks! In general I do expect from a Softwaretool an automated workflow as manually changing of statues is not very agile :-(

Thanks and BR

Verena

[Walter Buggenhout]

I understand your view, @Verena Schwegel. You may however be underestimating the power and flexibility of the tool a bit. Changing status is a part of workflow. What makes Jira such a powerful tool, is that every user can define their own statuses and transitions to match their exact business process. As a consequence, there is no way that the tool is capable out of the box to know what transition in the workflow of one issue type might trigger which other transition in another workflow.

That flexibility does seem pretty agile to me, but it does indeed mean you must take care of these automations as well! If your automations don't work out as of yet, mainly pay attention to the parent-child relations between your issues. The audit logs of your automation may help you identify why your rules aren't working as expected.