Automatically create new 'context-rich' Jira issues or subtasks, right from your workflow ... no coding required! → See Video
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.)
Reviews for cloud
(30)Sign in to write a review
Thanks for the feedback! In general, it should work with JIRA Service Desk and some users have done so without any unique enablement on our part. We are looking at additional things we may need do to improve support for use cases customers may have related to Service Desk. Best to open a support request if you feel there is something needed to better support use cases.
Reviews for server
(30)Sign in to write a review
Hello Alexander,
Thank you for your interest in Create on Transition for Jira Cloud. We are currently working on roadmap planning, and this is definitely a topic of discussion here. Even though we have had this request on our books for a period of time, I can tell you that it will get attention so please stay tuned. I see that you have already voted for the correct issue on our support platform. I would also suggest that you make yourself a watcher on that same issue, as this is where we will share the most up-to-date news. If you would like to reach out to me directly to discuss your needs further or just get a few more details, please feel free to do so using my contact information below.
Again, Alexander, we truly appreciate your feedback, and we look forward to hearing from you.
Regards,
Holly Wright, Marketing Director
Bob Swift Atlassian Add-ons (an Appfire company)
holly (at) appfire (dot) com
Thanks for the review! You mean a button to move a post function to the bottom of the list of post functions instead of just one position at a time? Yes that would be nice, but requires Jira to implement that ;).
Thanks for the feedback! In general, it should work with JIRA Service Desk and some users have done so without any unique enablement on our part. We are looking at additional things we may need do to improve support for use cases customers may have related to Service Desk. Best to open a support request if you feel there is something needed to better support use cases.
Pricing
| 10 users$10 | 25 users$120 | 50 users$200 | 100 users$400 | 250 users$600 | 500 & upAdditional pricing details |
Paid-via-Atlassian pricing FAQ
- How does server app pricing work?
Server products and apps 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 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 host product. For Jira Server 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 (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server 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.
- Do you offer academic, community, or open-source licenses?
For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps 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 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 host 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.
Bob Swift Atlassian Add-ons (an Appfire company) is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 6.1.0 • Jira Server 7.0.0 - 7.9.2 • Released 2017-08-07
Summary
Support time tracking fields
Details
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Create on Transition for Jira via search. The appropriate app version appears in the search results.
- 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.
- Enter your information and click Generate license when redirected to MyAtlassian.
- 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 apps
