Attachments getting Orphaned and cannot be Deleted when cloning a ticket

XMLWordPrintable

    • 2
    • Severity 3 - Minor
    • 7

      Issue Summary

      Orphaned attachments are created during cloning of the ticket and are not visible from the UI. JQL queries show that the attachments exist for a JSM Request, but cannot be deleted from UI.

      Steps to Reproduce

      • Add a comment with an attachment to a JSM Request
      • Use REST API to delete the attachment.
      • Run the following JQL search and the JSM request does not have the attachment.
        key in ("<JSM Request Key>") AND attachments is NOT EMPTY
        
      • Now clone the ticket with attachments.
      • Run the JQL search again and the JSM request is listed as having an attachment.
        key in ("<JSM Request Key>") AND attachments is NOT EMPTY
        

      Expected Results

      JQL results show JSM request does not have an attachment.

      Actual Results

      JQL results show that JSM request has an attachment.

      Notes

      Workaround

      • Raise a Support ticket to get the attachment Ids for the orphaned attachments.
      • Delete these attachments using the REST API Delete Attachment

            Assignee:
            Unassigned
            Reporter:
            Gautham
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: