Versions Compared

Old Version 30

changes.mady.by.user Deborah Scott

Saved on

compared with

New Version 31

changes.mady.by.user Deborah Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
bgColor#f5f5f5
titleColor#ffffff
borderWidth0
titleBGColor#000000
titleJSU for Jira Server/Data Center

This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation.

...

In such case "Copy Move Attachments" has to be placed between "Update change history for an issue and store the issue in the database" and "Re-index an issue to keep indexes in sync with the database"
Otherwise transition attachment will not be properly stored and it will be not attached to the current issue.

Info

If you use 'Move Attachments added during Transition' it is important that the 'Copy / Move Attachments' Post-Function is before JIRA Post-Function 'Update change history for an issue and store the issue in the database'!

Status
colourRed
titleException

expand

titleException from this rule is a situation when Transition issue is a destination issue


Warning

Due to a Bug in Jira JRASERVER-65939, 'Copy or Move Attachments' functionality, which are added through a Transition Screen, does not work in Jira 7.5.x & 7.6.0. If you require this functionality, please upgrade to minimum Jira Version 7.6.1!

...

When an identical attachment (same file name and same content) already exists in the destination issue, it will not be copied again. This is the case for both, existing and transition attachments.

Real life tips

...

Tips

 (tick) You might set up a special transition screen to mainly copy those attachments to all linked issues. So it feels more like it would be the create screen of the new issue. In that case, you won't show those fields on the origin issue, but reset them again afterwards afterward (just empty or back to the default value).

...