Versions Compared

Old Version 20

changes.mady.by.user IT Ops Notifications

Saved on

compared with

New Version 21

changes.mady.by.user IT Ops Notifications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
borderColor#C49045
borderWidth1
titleBGColor#ecd1a9
borderStylesolid
titleJSU for Jira Server

This is the documentation of JSU for Jira Server. If you are using JSU on Jira Cloud, you can find the documentation here.

...

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

Configuration

Image Added

Precondition

Include Page
precondition usage
precondition usage

...

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

Image Removed

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.


...

(info) Tip: You might setup 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 (just empty or back to the default value).