Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-63575

Provide a relationship at the data level that an attachment was uploaded via the commenting UI or not



    • Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Won't Fix
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      This issue was logged because it seems to be the fundamental thing in association of Attachments with Comments.  Being able to determine a directly uploaded attachment is also desirable.  None of this is current possible, leaving association down to informed guesswork.

      Currently (7.x+) attachment can be uploaded through the Issue screen directly, and the Commenting box.  We need to be able to differentiate these, which is not currently possible.

      The 'root' cause of this issue is that there is no association at the entity level between a Comment and an Attachment.  This is a fundamental requirement on which all historic issues that all would need this in order to be satisfied.

      Examples of possible workarounds are JRA-43448 to use timestamps to correlate on what attachments were added with a particular comment (unimplemented at this time).

      How it could work

      a) When the comment is submitted, the comment ID is set on the attachments that were uploaded through it.  

      b) When the comment is submitted the comment doesn't initially fire an event.  Attachments that were uploaded during the comment process have their timestamps reset (JRA-43448)

      This means that when a Comment event (that usually completes long after attachments have completed upload /creation) occurs, the related attachments can be located.

      Attachments uploaded directly are the problem case, as they could not be differentiated between the above.  We'd need to know they were uploaded directly.


        Issue Links



              Unassigned Unassigned
              cd3cc7134331 Andy Brook
              0 Vote for this issue
              2 Start watching this issue