Customers have installed this add-on in at least 1,267 active instances.
    by Bob Swift Atlassian Add-ons (an Appfire company) for JIRA Server 6.1 - 7.0.2 and more versions
    Versions available for JIRA Server 4.0 - 6.0.8
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.
    Atlassian Verified
    Bob Swift Atlassian Add-ons (an Appfire company) is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    Bob Swift Atlassian Add-ons (an Appfire company) supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Create new JIRA issues using powerful workflow functions

    Set issue fields

    Create multiple issues

    Conditions to control create

    Substitution variables are available from the issue being transitioned or its parent. They also allow you to set labels, add links, set watchers, copy attachments, and add a comment.

    You can create multiple issues, e.g., for each user in a list or for each component. JQL-based conditioning prevents the creation of duplicate issues when/if the transition is performed again.

    Regex pattern matching and JQL query information can be used to decide whether issue should be created or not based on issue field values.

    More details

    Create on Transition for JIRA provides workflow transition post functions that can be configured to create issues or subtasks. Create can be conditioned on information from the original or parent issue. Multiple Create On Transition post functions can be used to create multiple issues. The Create post function can also be associated with the create issue transition to automatically create issues or subtasks when an issue is created. This is a standard post function added and changed during workflow editing.

    (Shares similar capabilities with our Update on Transition for JIRA Add-on.)

    User reviews

    Sign in to write a review »
    by Mark Bensfield on 2015-11-16
    This was surprisingly quick and painless to set up for our company. It helps prevent a lot of manual work for me which is a godsend. I would upgrade from 3 to 4 stars if support for allowing you to copy existing comments from issues to the newly created one is added.
    Was this review helpful?YesNo
    by Yvan Le Texier on 2015-03-05
    Good plugin. Is there any way to create an issue on a remote JIRA instance (using application link) ? This would be an awesome feature.
    Was this review helpful?YesNo

    Vendor response

    Thanks for the review! https://marketplace.atlassian.com/plugins/org.swift.jira.acli covers the ability to create an issue on a remote JIRA. And https://bobswift.atlassian.net/browse/CSOT-312 tracks a more specific requirement.
    by Inga Dance on 2013-10-25
    If I have two JIRA instance: I have to buy two licenses?
    Was this review helpful?YesNo

    Vendor response

    Thanks for the rating. Yes, a license is required for each production instance. This is standard for all Atlassian paid plugins. A development/test instance license is included with a production license and can be found on your my.atlassian.com account.
    by Martin on 2013-09-04
    We'd love to use this plugin - any plans to make it available for OnDemand users?
    Was this review helpful?YesNo

    Vendor response

    Thanks :). There are no current plans for OnDemand support. Tracked as CSOT-136 . 


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 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 host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

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

    Add-on purchase and renewal is half-price if you have an academic license for your Atlassian host application. Add-ons are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

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

    Learn more


    Bob Swift Atlassian Add-ons (an Appfire company) is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Bob Swift Atlassian Add-ons (an Appfire company) supports Create on Transition for JIRA. You can visit the support site to get help.

    Get support


    Version 5.4.1 JIRA Server 6.1 - 7.0.2 Released 2015-10-12


    JIRA 7.0 support, custom labels field type support, radio field type fix


    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 add-ons from the left-hand side of the page.
    4. Locate Create on Transition for JIRA via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Create on Transition for JIRA. You're prompted to log into MyAtlassian. Create on Transition for JIRA 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 Create on Transition for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons