- Jira Service Management
Getting high business value by keeping status of issues in sync for transparency: epic/stories, parent/subtasks or linked issues
Synchronized, distributed workflows
Getting high business value by automating transitions in complex scenarios to reduce manual efforts and failures and to react in real-time using distributed but synchronized workflows: simple usage but very effective!
Workflow functions for synchronization
Easily add and configure synchronization of statuses for linked issues in all enterprises having to fulfill certain reglementary requirements where it is necessary to administrate workflows for all projects, centralized.
Users get benefit from automated synchr. of status
Having configured workflow status synchronizations, users do not have to do anything but enjoy less manual clicking: different levels of issue hierarchies are kept in sync automatically. Focus on the essentials!
Using Jira Core, Jira Software or Jira Portfolio, you end up having hierarchies of issues. Generally, this issues are of different issue types having their own workflows and statuses. 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: set status of EPIC to "in progress" if first user story is started
- Scenario B: 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: 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
- other scenarios are possible to automate triggers: top-down or bottom-up.
Privacy and security