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

Ability to rename attachments

XMLWordPrintable

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

      It would be very helpful in JIRA to be able to rename an attachment, just like you are able to do in Confluence. This is especially beneficial when attachments are created from Capture since the names are not very meaningful and can also happen when users take quick screenshots to attach.

      Currently, I have to download the attachment, rename, upload, and then delete the previous one - with email notifications and no way to control them for attachments, this process triggers a couple of emails each (new and delete)

      When changing an attachment property, please don't have it trigger an email notification, though!

            [JRASERVER-37835] Ability to rename attachments

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3042448 ] New: JAC Suggestion Workflow 3 [ 3669727 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2617939 ] New: JAC Suggestion Workflow [ 3042448 ]
            Gosia Kowalska made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Resolved [ 5 ]

            Gosia Kowalska added a comment -
            Atlassian Update – 20 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 20 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2587455 ] New: Confluence Workflow - Public Facing v4 [ 2617939 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2362473 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2587455 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2130172 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2362473 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093651 ] New: JIRA Bug Workflow w Kanban v6 [ 2130172 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 881919 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093651 ]
            jonah (Inactive) made changes -
            Description Original: It would be very helpful in JIRA to be able to rename an attachment, just like you are able to do in Confluence. This is especially beneficial when attachments are created from Capture since the names are not very meaningful and can also happen when users take quick screenshots to attach.

            Currently, I have to download the attachment, rename, upload, and then delete the previous one - with email notifications and no way to control them for attachments, this process triggers a couple of emails each (new and delete)

            When changing an attachment property, please don't have it trigger an email notification, though!             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-37835].
              {panel}

            It would be very helpful in JIRA to be able to rename an attachment, just like you are able to do in Confluence. This is especially beneficial when attachments are created from Capture since the names are not very meaningful and can also happen when users take quick screenshots to attach.

            Currently, I have to download the attachment, rename, upload, and then delete the previous one - with email notifications and no way to control them for attachments, this process triggers a couple of emails each (new and delete)

            When changing an attachment property, please don't have it trigger an email notification, though!

              Unassigned Unassigned
              4f4250feead3 Karie Kelly
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: