Summary

It is easy to copy attachments to the newly created issue from the original issue (issue being transitioned) or other issues by using the Attachments field. However, special care is required if you want to copy new attachments from the original issue that have been added by the user on the transition screen. The reason for this is that some actions requested in your configuration have to be done after the issue is created and that requires that JIRA has fully registered the issue in the database and this is of the system defined post functions.

Solution

My solution: move the post function below the post function that updates the issue and store the issue in the database.

Set issue status to the linked status of the destination workflow step.
Add a comment to an issue if one is entered during a transition.
Update change history for an issue and store the issue in the database.
Create subtask
Create subtask
...
Re-index an issue to keep indexes in sync with the database.
Fire a Generic Event event that can be processed by the listeners.

My solution: move the post function below the post function that updates the issue and store the issue in the database.

Set issue status to the linked status of the destination workflow step.
Add a comment to an issue if one is entered during a transition.
Update change history for an issue and store the issue in the database.
Create subtask
Create subtask
...
Re-index an issue to keep indexes in sync with the database.
Fire a Generic Event event that can be processed by the listeners.

Create on Transition for Jira

How to copy new attachments to created issue

Analytics

Summary

Solution

Related content