Enhancements

‘Copy sub-tasks' option re-enabled on Create/Clone issue post function

When using calculated issue types, the option to copy sub-tasks to new issues has been re-enabled for the Create/Clone issue(s) post function. If the calculated issue type does not support sub-tasks, and error will be logged.

Multi-level Cascading Select support

Support for custom fields added using the marketplace app Multi-leve Cascading Select has been added. When using a post function to copy values from these custom fields, you can now copy their values no matter which level value is selected in the source issue.

Bug fixes

• Extensions

  • Interactions between third-party custom fields and the Copy issue fields post function have been overhauled: a new option - “Use raw value” - has been introduced to copy the field values without any data processing, which can help when setting values for custom fields provided by other apps.

  • In some scenarios, the Set issue fields post function failed to update parent or child issues when copying the Watchers field. This has been fixed.

  • The Assign Issue post function failed to find a matching user when using a script to retrieve potential assignees if there were multiple partial matches. This has been resolved.

  • Extensions that use link types (for example, Comment related issues, Related issue(s) Validator, and Related issue(s) Condition) were not editable and could not be deleted if the link type used in their configuration was deleted. This has been resolved and these extensions can now be updated or removed.

  • The Create/Clone issue(s) post function was incorrectly ignoring the Run as setting for the purpose of adding Comments after issue creation. This has been fixed.

  • The Set issue fields post function would not display in the workflow editor or in the JMWE Workflow extensions administration page if it included a custom field that was later deleted. This has been resolved.

  • Testing JQL expressions from the configuration page of the Create/Clone issue(s) post function, Related issue status condition, Related issue status validator, and Link issues to the current issue post function were showing errors when editing a pre-existing extension. This issue was resolved.

• Event-based Actions

  • Event-based Actions with the “Issue transitioned” trigger were running multiple times when the Assignee value was updated during the transition. This has been resolved.

• Scheduled Actions

  • Scheduled Actions that were disabled displayed a message that the action had been executed even though it had not. This has been fixed.

• Migration

  • The downloadable pre-migration spreadsheet included all projects, workflows, and extensions, even when only a specific project was selected for migration. This has been resolved.

Credits

Thank you our valuable customers!

We want to thank you, our incredible, supportive customers, for using our apps. You have provided great feedback and want you to know that you truly are the reason why we build software!