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

Table of Contents


Info

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

...

A user defines which issue should be a source and which is a destination. 

Any number of attachments can be copied to the related issue/-s.

Configuration

Image RemovedImage Added

Precondition

Include Page
precondition usage
precondition usage

...

You have several different options, which defines define which issue/s will be treated as source/destination for attachments.

Several of JSU's workflow modules provide the option the to define the scope of the module on some related issues.
For example, instead of copying attachments from one issue to the others another, you might choose to copy them from all linked issues to the issue in transition (e.g. to group all attachments within one issuesissue)

Types of issue relations

Related issue issues will be found by one of the following JIRA following Jira concepts:

  • Issue Link
    You can define the link type to defined which issues exactly will be affected by the operation.
    Since JSU 2.2.0, we introduced the value ANY. The operation will be performed on any linked issues.
  • Parent / Sub-Task
    The related issue is either parent or sub-task of each other.
  • Epic / Issue in Epic
    (info) This is only applicable , if you have JIRA have Jira Software installed.
    The other issue is either the epic related by an epic link, or it is part of an epic.

...

Or in other words that issue , which triggered a workflow condition/validator/post function to be executed.

...

Here the idea is, that you have a checkbox custom field on the transition screen, so the user can control some of the functionality.

Image RemovedImage Added

For example a checkbox 'Copy Existing Attachments' might be configured as Custom Field that enables copying existing attachments. Only if it is ticked, all attachments will be copied.
Typically this checkbox custom fields won't appear in the normal screen of the 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

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.


...