Versions Compared

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 for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation.

On this page:

Table of Contents
minLevel1
maxLevel3
Info

The 'Copy / Move Attachments' feature is available from JSU 2.9.0

Description

This The ‘Copy or Move Attachments’ post function will copy copies attachments from/to all related issues. A user defines You can define which issue should be a source and which is a destination. Any number of attachments can be copied to the related issue(s).

...

Precondition

If you are using preconditions with a JSU post function, you can use the following options to define how the precondition is evaluated:

...

You have several options which define which issue/s will be treated as a source/ or destination for attachments. Related issues are evaluated by one of the following Jira concepts:

  • Issue Link: You can define select the link type to define which issues exactly will be affected by the operation. From JSU 2.2.0, we introduced the value ANY. The operation will post function action. Select ANY if you want the action to be performed on any linked issues.

  • Parent / Subtask:The related issue is either parent or subtask of each other.

  • Epic / Issue in Epic:This is only applicable if you have Jira Software installed. The other issue is either the epic related by an epic link, or it is part of an epic.

  • JQL: A JQL query will be executed to retrieve the issues. You can use placeholders in the JQL query which will be replaced with the current field values of the issue in transition. For tips on writing the JQL query, see JQL Reference.

...

Note

If you use Move Attachments added during Transition it is important that the 'Copy / Move Attachments' post function is before Jira’s 'Update change history for an issue and store the issue in the database' post function.

In such cases the ‘Copy Move Attachments’ must 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, the transition attachment will not be properly stored and it will be not attached to the current issue.

...