Page Comparison

...

...

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  Any number of attachments can be copied to the related issue/-(s).

Configuration

...

Precondition

...

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

• Ignore precondition (default): Every precondition is ignored which means that the post function will always be performed

• True: Precondition must be true to execute a post function

• False: Precondition must be false to execute a post function

Issue relation

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

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

Types of issue relations

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

• Issue Link

  
  

  : You can

  define

  select the link type to

  defined

  define which issues

  exactly

  will be affected by the

  operation.
  Since 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 /

  Sub-Task
  

  Subtask:The related issue is either parent or

  sub-task

  subtask of each other.

• Epic / Issue in Epic

  
   This

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

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

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 You can 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 to that workflow module. For example Create a Linked Issue will just create a new issue and then connect it with some Issue Relation to the issue in transition

Perform As User

With Perform As User, you can specify a different user account that owns the necessary permissions. Usually, this user account is assumed to be only technical (impersonation), with broad permissions, but not used to log in to a Jira account as a person. 

If you don't specify a user here, the transition on the related issue is performed as the same user who triggered this post function on the origin issue by default. Therefore that user must have the necessary permissions on the related issue. In some restrictive setups, that user might not have the permissions on the related issue or even might not have access to the project of the related issue.

In combination with the User is in Any Users condition, you can hide a transition from all users other than the 'Perform As User' user.

Controlled by custom field

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

...

For example, a checkbox 'Copy Existing Attachments' might be checkbox is configured as Custom Field a custom field that enables copying existing attachments. Only if If it is tickedselected, all attachments will be copied.
Typically this checkbox custom fields field won't appear in on the normal issue screen of the issue. Instead of letting the allowing a user to choose to copy/move the attachments, you can also configure it to either never /or always copy them. Tip: You might choose '

Move option

If you choose the Move option for 'Copy/Move Attachments added during Transition'. The , when a user then adds some attachments on the transition screen of the source issue. However since they are moved to all related issues, it feels appears as if he just they added the attachments to all related issues. 

Position of the

...

post function

Jira transitions include essential post functions that are executed in a specific order. When adding JSU post functions to a transition it is important to position the post function with respect to the essential post functions.

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

This post function can be also used in a combination with preconditions.

...

’

...

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

...

See Also

• Workflow Preconditions

• Precondition Configuration

• Perform As User