Cloud Migration Resources
Planning a Jira Cloud migration? These resources can help you get started:
→ JSU Cloud features – Review Cloud features and understand key differences between DC and Cloud.
→ Migration support from Appfire – Learn how we can help you migrate smoothly.
Copy or Move Attachments post function
Description
The Copy or Move Attachments post function copies attachments from/to all related issues. You can define which issue should be a source and which is a destination. One or more attachments can be copied to the related issue(s). You can also use the post function to move attachments added on a transition screen.
See Workflow post functions to learn how to add a JSU post function to a Jira workflow.
Configuration
Precondition
If you are using preconditions with a JSU post function, they can be evaluated in the following ways:
True (Precondition must be true to execute a post function)
False (Precondition must be false to execute a post function)
The precondition setting is available on our post function configuration pages, and it is set to True by default. You can learn more about our preconditions in Workflow Preconditions. See the Preconditions for Post Functions uses cases for examples.
Issue Relation
Perform As User
Perform As User is a configuration option in JSU post functions. It lets you choose the user who acts on the post function when it runs. When choosing a user account to run a post function, the specified user account must have the appropriate permissions to perform the actions, such as creating an issue or adding a comment.
Copy attachment from/to any related issue
You have different options for defining which issue/s will be treated as source/destination for attachments. Several of JSU's workflow modules provide the option to define the scope for 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.
Conditional copying attachments
Conditional copying attachment (controlled by custom field) is always only checked for issues in transition, regardless of whether the issue in transition is a source or destination.
Related pages
https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518573
https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518511