22
Customers have installed this app in at least 22 active instances.
    by syracom AGfor Jira Server 7.4.0 - 8.1.0 and more versions
    Versions available for Jira Server 7.0.0 - 7.3.9
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    syracom AG supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.

    Getting high business value by keeping status of issues in sync for transparency: epic/stories, parent/subtasks or linked issues

    Getting high business value by keeping status of issues in sync for transparency: epic/stories, parent/subtasks or linked issues

    Getting high business value by keeping status of issues in sync for transparency: epic/stories, parent/subtasks or linked issues

    Synchronized, distributed workflows

    Workflow functions for synchronization

    Users get benefit from automated synchr. of status

    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!

    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.

    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.

    Reviews for cloud

    (3)Sign in to write a review

    There are no reviews yet. Be the first to review this app.

    Reviews for server

    (3)
    Sign in to write a review
    by Marco Guillermaz on 2018-06-08
    Great plugin ! Very useful ! Please, update for the compatibility with JIRA 7.10.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo

    Reviews for Data Center

    (3)Sign in to write a review

    There are no reviews yet. Be the first to review this app.

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    10 users$1025 users$2550 users$50100 users$100250 users$250500 & upAdditional pricing details

    Pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

    Can I install this app in a Data Center product?

    This app does not have a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.

    However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.

    Learn more about Data Center licensing

    Do you offer academic, community, or open-source licenses for server apps?

    For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are available for server apps. Learn more about community and open source licenses.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.

    How can I buy apps for my legacy Jira Server or Confluence Server license?

    If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    syracom AG provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 1.4.1 Jira Server 7.4.0 - 8.1.0 Released 2019-03-08

    Summary

    Compatibility release

    Details

    • Compatibility for Jira 8.x

    Installation

    1. Log into your Jira instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new apps or Find new add-ons from the left-hand side of the page.
    4. Locate Status-Sync for distributed workflows via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Status-Sync for distributed workflows. You're prompted to log into MyAtlassian. Status-Sync for distributed workflows begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.

    To find older Status-Sync for distributed workflows versions compatible with your instance, you can look through our version history page.

    Similar apps