Page Comparison

...

...

Description

This post function will copy attachments from/to all related issues.

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

...

Precondition

Copy attachment from/to

...

any related

...

issue

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
   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.

Issue in transition

We use the term 'Issue in Transition' when we refer to the issue for which a workflow condition is checked, for which a workflow validator is examined, or for which a workflow post function is performed.

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

Source and destination

For example, the Copy Value From Other Field Post-Function allows you to define the issue in transition as the source or destination of the copy operations, while you define the other end with an issue relation.
The field value will then be read from the source issue and be written to the destination issue.

Other workflow modules do not have source and destination. So you just define the issue relation, which will apply for that workflow module.
For example example, Create a Linked Issue will just create a new issue and then connect it with some Issue Relation to the issue in transition.

...

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 Removed

...

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.

...

 Tip: You might choose 'Move Attachments added during Transition'. The user then adds some attachments on the transition screen of the source issue. However, since they are moved to all related issues, it feels as if he just added the attachments to all related issues. 

Perform As User

Position of the Post Function

If you use 'Move Attachment' (see bellowbelow) you must position the post function before 'Update change history for an issue and store the issue in the database.'

...

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.

Already existing attachments are not copied again

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

  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).