Skip to:

Status-Sync for distributed workflows

works with Jira Server 8.0.0 - 8.13.8 and more

OVERALL RATINGS

We no longer offer sales and support for server apps. You can stay connected by exploring the migration options to either the cloud or Data Center version of this app.

Explore migration program

Key highlights of the appGetting 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!

More details

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.

Resources

Privacy and Security

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Version information

We no longer offer sales and support for server apps. You can still explore the earlier versions but these may not offer the necessary support.

Explore all server versions

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow