Versions Compared

Old Version 18

changes.mady.by.user IT Ops Notifications

Saved on

compared with

New Version 19

changes.mady.by.user IT Ops Notifications

Saved on

Key

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

Table of Contents

...

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.


...

Already existing attachments are not copied again

When an identical attachment (same file name and same content) already exists for in the destination issue, it will not be copied again. A dedicated algorithm compares file names, sizes, byte codes to decide if source attachment should not be copied again to a destination issue. The algorithm works both for This is the case for both, existing and transition attachments.

...