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.

Release Notes 6.1

Release Notes 6.0

Release Notes 5.8

Release Notes 5.7

Release Notes 5.6

Release Notes 5.5

Release Notes 5.4

Release Notes 5.4

Release Notes 5.3

Release Notes 5.2

Release Notes 5.1

Release Notes 5.0

Release Notes 4.5

Release Notes 4.4

Release Notes 4.3

New options

• Option to copy attachments from another issue
• Option to add a comment
• Option to set specific issue type and priority using substitution variables
• Option for documentation notes to improve workflow maintainability

More substitution variables

• Substitution variable for project category
• Substitution variables for issue type and priority
• Substitution variables for other system fields supporting parent or original issue prefixes
• Function based substitutions
  • earliestUnreleasedVersion
  • latestReleasedVersion

Support Latest Jira Release

• Tested against Jira 6.1 EAP

Support More Complex Scenarios

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.

• Create multiple subtasks on transition that have different assignees
• Provide substitution variables for custom field option values.
• Support multi-select fields on set custom field
• Support cascade select fields on set custom field

Date Handling Improvements

• Accept alternative date format when parsing date values. This allows easier use of substitution variables in other date fields. 
• Allow date substitution replacement values to be formatted to a configured format.
• Log errors in the server log for date conversion errors and other exceptions that occur when a custom field cannot be set as requested.

Improvements and Fixes

• Allow project to be constructed from substitution variables
• Allow simple field name mapping on Copy custom fields parameter. This makes it easier to copy one field to another. Field values must be compatible. To map field names on the copy, use syntax like: from custom field name:to custom field name.
• Allow copying of original issue custom fields in addition copying parent issue custom fields that were supported earlier.

Jira 6.0

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.

Substitution variables for original issue custom fields

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.

Create Multiple Issues or Subtasks

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.

JQL Query Substitution Variables

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.

Group and Role Substitution Variables

Additional substitution variables that can help with conditioning, setting field values, and creating multiple issues.

Improvements and Fixes

1. Fix for sibling create getting wrong parent.
2. More consistent and documented substitution variables.
3. Support multi-line custom fields.
4. Allow ids for issue security lookup.

Create Issues

1. Ability to create issues similar to creating subtasks.
2. Almost all options are similar to creating subtasks.
3. New option for setting target project. Default is the project associated to original issue.
4. New option for setting issue security level.
5. Link to original issue is optional, configure the Link parameter setting if you need a link.

Jira 6.0 Support

Improvements and Fixes

1. Improved permission handling.

New Options

1. Set labels with replacement variables for parent_labels and original_labels.
2. Set watchers with replacement variables for parent_watchers and original_labels.
3. Add a link from the created issue to another issue with the ability to control the link type and direction.

More Conditioning Options

1. Exact match option as a more stringent condition versus the default find matching for more fine grained control over the condition.
2. Literal option to treat the pattern as a literal string. Makes it easier for simple conditions - don't have to worry about escaping special regex characters.
3. Negative (or Reverse) option. Make it easy to specify a condition that when matched will prevent the issue from being created.

Improvements and Fixes

1. Custom fields will be set to default value if not otherwise set.

New feature - conditioning

Post function author can provide criteria to condition whether or not a subtask should be created based on information in the original issue.

Commercial plugin

This is now an Atlassian paid plugin. See this announcement. This will help assure customers of ongoing support and future improvements.