Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-43448

When attachments are uploaded as part of a transition they get the upload timestamp as their creation date



    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


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

      Given that during a transition, users dynamically upload attachments, and then type a comment, what results is a 'spread' of attachment creation times, potentially many minutes apart, making identification of them difficult as being 'related' the user action / transition that resulted in an IssueEvent.

      So, with a user uploading the odd file, having a coffee, and thinking long and hard about the related comment, the Event Listener has no real idea of what attachments were stored as part of that transition. It would be reasonable (I thought) to assume that any attachment added within the last N seconds to the corresponding issue would be related to the current event, however, given the spread above, its not possible to 'tightly' identify by attachment creation time, which were created 'most likely' by the current event.

      Is there a reason that the attachment creation timestamp reflects the point at which they were uploaded, rather than when the user hits submit on the transition screen?

      Ideally, all attachments uploaded would have the same timestamp of the point at which the transition screen Submit occurred?

      Alternatively, it would be super-useful for the transition related variables to be available in issue events, which they currently aren't.


        Issue Links



              7645729f7e9f Arbaaz Gowher
              cd3cc7134331 Andy Brook
              5 Vote for this issue
              4 Start watching this issue