Customers have installed this add-on in at least 5 active instances.
    by Alkaes Consultingfor JIRA Server 6.2 - 7.2.8
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Alkaes Consulting supports this add-on.

    Get support

    Get it nowFree add-on

    Its CopyTo action allows you to restore your Workflow as it has been designed, before being altered by a publication : JRA-38337

    Its CopyTo action allows you to restore your Workflow as it has been designed, before being altered by a publication : JRA-38337

    Your Workflow with Recursive Global Transition

    Workflow altered since JIRA 6.x

    Direct copy of XML Descriptor between 2 Workflows

    By using the previous Workflow Editor (Flex version) and some small edit in the XML descriptor, we are able to implement Recursive Global Transitions.

    It was resolving many issue in our Workflow Design.

    Since JIRA 6.x, Workflows were altered on publication.

    Instead of 1 transition, you'll have x number of transitions to manage.

    In order to keep your Workflows as you designed it (with Recursive Global Transitions), you can override a published Workflow with its copy before the Publish / Assign operation

    More details

    This plugin provides a workaround related the issue https://jira.atlassian.com/browse/JRA-38337.

    With JIRA 6.x, as soon you publish a Workflow that contains some Recursive Global Transition, it is altered by splitting each of these transition into many Step Transition (1 per step).

    It means than instead managing one Global Transition, you will have to manage n Step Transitions.

    This plugin allow you to restore your initial Workflow after publication ...

    Before publishing a new Workflow or assigning it into a Draft Workflow Scheme, keep a copy. This copy will stay as an inactive Workflow.

    And after the publication, your Worklow is now altered by JIRA.

    You can recopy this inactive Workflow using the action "Copy to", directly by overriding its descriptor into the published Workflow.

    User reviews

    Sign in to write a review
    by Matt Doar [ServiceRocket] on 2015-01-05
    Please would you add a link somewhere in the docs to the original issue in j.a.c about this. To make the reason for it clearer.
    Was this review helpful?YesNo
    Alkaes Consulting
    Hi Matt, Thanks for highlighting this lack. The goal of this plugin is just to provide a quick workaround of the conversion of Recursive Global Transitions into Step Transitions, as detailed in JRA-38337.


    Alkaes Consulting provides support for this add-on.

    Vendor support resources


    Find out how this add-on works.

    Atlassian Community

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


    Version 1.0.2 JIRA Server 6.2 - 7.2.8 Released 2015-02-10


    Bug fixing


    In previous version, the encoding of Workflow XML descriptor was not fully forced to UTF-8. It causes that after copy the encoding was switched to the Encoding of the System, not necessary in UTF-8.


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Alkaes Plugin Workflows Tools for JIRA via search. Results include add-on versions compatible with your JIRA instance.
    5. Click Install to download and install your add-on.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Alkaes Plugin Workflows Tools for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons