Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-32848

Initial Attachment history to be recorded either in History / Activity tab

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • 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.

      Came across the following ticket that was discussing about this matter:

      It might be quite confusing as the initial creation of a ticket that has an attachment included in it is not recorded in the History tab. However, the next attachment included in the ticket is recorded. The only way to check on this is through the Manage Attachments option. Is this an intended behavior? The following screenshot(s) explain:

      • Creating a new issue with the attachment jira.jpg attached to the issue

      • Checking the Activity tab and History tab, nothing is recorded

      • Checking through Manage Attachments, you are able to see the details of the attachment
      • After including another attachment greenhopper.png to the ticket, then you can see the changes

        1. activity_tab.JPG
          92 kB
          Ahmad Danial
        2. activity_tab_2.JPG
          89 kB
          Ahmad Danial
        3. create_issue_1.JPG
          59 kB
          Ahmad Danial
        4. create_issue_2.JPG
          58 kB
          Ahmad Danial
        5. history_tab.JPG
          88 kB
          Ahmad Danial
        6. history_tab_2.JPG
          98 kB
          Ahmad Danial
        7. manage_attachment.JPG
          30 kB
          Ahmad Danial

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: