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

Rename email attachments if an attachment with the same filename already exists.

    • 1
    • 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.

      When I attach screenshots to an issue, I usually do this by email. The images included in the email seem to be named sequentially, presumably by my email client e.g. "image1.jpg". When I go to attach a second screenshot in the same manner, the second image has the same filename. This causes a couple of problems. Any links within comments including the first file now point to the second file. I can't include a thumbnail of the second file inline in a comment. This issue could be resolved by automatically renaming the file on the server to something unique.

            [JRASERVER-36701] Rename email attachments if an attachment with the same filename already exists.

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3059735 ] New: JAC Suggestion Workflow 3 [ 3688949 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2604035 ] New: JAC Suggestion Workflow [ 3059735 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2591705 ] New: Confluence Workflow - Public Facing v4 [ 2604035 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342556 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2591705 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2111071 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2342556 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2081208 ] New: JIRA Bug Workflow w Kanban v6 [ 2111071 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 882970 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2081208 ]
            jonah (Inactive) made changes -
            Description Original: When I attach screenshots to an issue, I usually do this by email. The images included in the email seem to be named sequentially, presumably by my email client e.g. "image1.jpg". When I go to attach a second screenshot in the same manner, the second image has the same filename. This causes a couple of problems. Any links within comments including the first file now point to the second file. I can't include a thumbnail of the second file inline in a comment. This issue could be resolved by automatically renaming the file on the server to something unique. New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-36701].
              {panel}

            When I attach screenshots to an issue, I usually do this by email. The images included in the email seem to be named sequentially, presumably by my email client e.g. "image1.jpg". When I go to attach a second screenshot in the same manner, the second image has the same filename. This causes a couple of problems. Any links within comments including the first file now point to the second file. I can't include a thumbnail of the second file inline in a comment. This issue could be resolved by automatically renaming the file on the server to something unique.

              Unassigned Unassigned
              6e27fdb07099 Ben Ernst
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: