The 7.2 release includes:
Read more in the full release notes.
The 7.2 release includes:
Read more in the full release notes.
We've made massive investments in infrastructure and testing frameworks for our Data Center apps to ensure that they will scale to meet the needs of your enterprise team. Create on Transition for Jira Data Center has been rigorously tested and vetted for consistent, efficient, and reliable performance at scale.
For more information, read the full release notes.
Our server apps have always been Data Center compatible, and with the release of Atlassian’s new Data Center approved apps program, we've made massive investments in additional infrastructure and testing frameworks for our Data Center apps to ensure that they will scale to meet the needs of enterprise teams. These apps have been rigorously tested and vetted for consistent, efficient, and reliable performance at scale.
If you’re currently using Jira Data Center or thinking about upgrading, check out the Data Center approved version of Create on Transition.
Additionally, this release also includes some minor fixes.
For more information, read the full release notes.
What's new in version 7?
Easily set up post functions in a tabbed interface — Wave goodbye to the long, cumbersome configuration screen and say hello to a neatly-organized menu that groups related parameters together for easier navigation.
Save time with smart drop-downs and auto-fill fields — Plus, with added help text, an upgraded custom field builder, and loads of other usability improvements, Create on Transition is more intuitive than ever!
Read more in the full release notes.
New in this release
As a workflow designer, you have to think about the users that run the transitions and the permissions they have to have to do some of the things you want the transition to accomplish. This support allows you to have the action work as if it is being done by another user. This means that different permissions can apply.
Fixed in this release
User have been discovered that the support for creating multiple issues can be used in many ways. These improvements will help cover more complex scenarios.
This release is functionally equivalent to Release 3.4. Since 3.2, the plugin has been tested on EAP drivers of Jira 6.0. This release fixes CSOT-86 on Jira 6.0. This required moving the target level to Jira 5.2 and above. Future releases of Create on Transition Plugin for Jira will now target Jira 5.2 and 6.x.
Custom field names specified as replacement variables are evaluated from the parent issue. This improvement provides a way to specify a custom field from the original issue for the case of sibling create of a subtask. This accomplished by using original_ prefix on the custom field name or id. See Substitution variables.
This ability to create multiple similar issues or subtasks with one configuration is especially important when the number to create is dependent on information from the original or parent issue. For example, creating one subtask for each fixed version for an issue. See How to create multiple issues or How to create multiple issues - advanced example for more details.
An option to run a JQL query has been added. The results of the query can be used as substitution variables for conditioning, setting field values, and creating multiple issues. How to create multiple issues - advanced example shows how this can be used.
Additional substitution variables that can help with conditioning, setting field values, and creating multiple issues.
Post function author can provide criteria to condition whether or not a subtask should be created based on information in the original issue.
This is now an Atlassian paid plugin. See this announcement. This will help assure customers of ongoing support and future improvements.
