Introduction to synchronized but distributed workflows
In a lot of different business scenarios, you end up having hierarchies of issues like EPIC and related user stories using JIRA Software or issue hierarchies represented by issue links like within JIRA Portfolio or just subtasks of issues within JIRA Core. Generally, this issues are of different issue types having their own workflows and statuses. Issues on higher hierarchy levels are more general wheres as issues on lower hierarchy levels are more fine-granular. Nevertheless there are points in time, sometimes named "quality gates", when status of different issue levels should be synchronized. You can do this manually, but it is failure-prone and not effective. Just imagine the following scenarios:
- Scenario A: automatically, set status of EPIC to "in progress" if first user story is started
- Scenario B: automatically, set status of EPIC to "is developed" if all user stories are ready for testing. Next step of the EPIC may be "start integration test" triggering workflow transition "start test" of the related test-task switching into status "testing".
- Scenario C: automatically, set status of all user stories to "cancelled" if related EPIC is switched into status "cancelled" in order not to spent more time and budget into this stories
- Many other scenarios are possible to automatically trigger a status change of one or all issues on a different hierarchy level: top-down or bottom-up.
A synchronized, distributed workflow for EPIC and related User Stories may look like the following sample:
Configure workflow post functionsExtend your workflow(s) Related pagescontentbylabel
|cql||label = "documentation-space-sample" and type = "page" and space = "STATUSSYNC"|