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

Need ability to see change history of edited comments

XMLWordPrintable

    • 240
    • 27
    • Hide
      Atlassian Update - 17th of October  2024

      Hi everyone,

      Thank you for your suggestion and for taking the time to share your thoughts with us. After careful consideration, we have decided not to proceed with this feature request at this time.

      We’re currently focusing on other areas of the product and prioritize those that provide the most value to the majority of our users that includes Performance and Scale and Security updates.

      Please remember that [jira.atlassian.com] is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira DC roadmap and the Atlassian DC release notes blog.

      We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.

      Rudy Slaiby
      Product Manager, Jira Data Center

      Show
      Atlassian Update - 17th of October  2024 Hi everyone, Thank you for your suggestion and for taking the time to share your thoughts with us. After careful consideration, we have decided not to proceed with this feature request at this time. We’re currently focusing on other areas of the product and prioritize those that provide the most value to the majority of our users that includes Performance and Scale and Security updates. Please remember that [jira.atlassian.com] is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira DC roadmap and the Atlassian DC release notes blog. We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback. Rudy Slaiby Product Manager, Jira Data Center
    • 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.

      Problem Definition

      JIRA-1100 introduced editable comments. This is great. When our security officer reviewed the feature he wanted access to the change history, which would be important in the event of a security audit. It appears that there is no way to view comment history.

      Suggested Solution

      The ability to view comment change history. Ideally, this would be implemented such that a new permission was added 'View comment change history' so that its implementation could be configured at the site level.

        1. email_comment_history.png
          15 kB
          Peter von Hofer

            [JRASERVER-12400] Need ability to see change history of edited comments

            Renata Dornelas made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 760715 ]

            Johannes Schwedhelm added a comment -

            Hi ayakovlev@atlassian.com , agree to former comments. This is far more a QA hygiene topic than a feature request.

            Question: how many votes of user feedback is necessary? 759 for now seems a pretty high number. thx

            Johannes Schwedhelm added a comment - Hi ayakovlev@atlassian.com , agree to former comments. This is far more a QA hygiene topic than a feature request. Question: how many votes of user feedback is necessary? 759 for now seems a pretty high number. thx

            Aniceto Goñi Díaz de Cerio added a comment -

            Another dissapointing decision by Atlassian TM

            I think I have lost the count already... that's too many basic features that they have 'decided not to proceed' with. At the same time, licence fees are higher every year, and the investment is harder to justify every year.

            Might be looking for a replacement app in the future.

            Aniceto Goñi Díaz de Cerio added a comment - Another dissapointing decision by Atlassian TM I think I have lost the count already... that's too many basic features that they have 'decided not to proceed' with. At the same time, licence fees are higher every year, and the investment is harder to justify every year. Might be looking for a replacement app in the future.

            Michael Mohr added a comment -

            Hi Rudy Slaiby,

            stating: "We’re currently focusing on other areas of the product and prioritize those that provide the most value to the majority of our users "

            and at the same time ignoring nearly 1000 votes on this issues for now over 17 years is a impudence!

            Formerly one of Atlassian pillars was "Don't f..k the customer". This meanwhile seems to be reversed meanwhile by Atlassian!

            Michael Mohr added a comment - Hi Rudy Slaiby, stating: "We’re currently focusing on other areas of the product and prioritize those that provide the most value to the majority of our users " and at the same time ignoring nearly 1000 votes on this issues for now over 17 years is a impudence! Formerly one of Atlassian pillars was "Don't f..k the customer". This meanwhile seems to be reversed meanwhile by Atlassian!
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-12400].
            {panel
            h3. Problem Definition
            JIRA-1100 introduced editable comments. This is great. When our security officer reviewed the feature he wanted access to the change history, which would be important in the event of a security audit. It appears that there is no way to view comment history.

            h3. Suggested Solution
            The ability to view comment change history. Ideally, this would be implemented such that a new permission was added 'View comment change history' so that its implementation could be configured at the site level.
            		New: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-12400].
            {panel}

            h3. Problem Definition
            JIRA-1100 introduced editable comments. This is great. When our security officer reviewed the feature he wanted access to the change history, which would be important in the event of a security audit. It appears that there is no way to view comment history.

            h3. Suggested Solution
            The ability to view comment change history. Ideally, this would be implemented such that a new permission was added 'View comment change history' so that its implementation could be configured at the site level.
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: {panel:title=Atlassian Update - 17th of October  2024|borderStyle=solid|borderColor=#2684ff|titleBGColor=#2684ff|bgColor=#ffffff}
            Hi everyone,

            Thank you for your suggestion and for taking the time to share your thoughts with us. After careful consideration, we have decided not to proceed with this feature request at this time.

            We’re currently focusing on other areas of the product and prioritize those that provide the most value to the majority of our users that includes Performance and Scale and Security updates.

            Please remember that [jira.atlassian.com] is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira DC roadmap and the Atlassian DC release notes blog.

            We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.

            Rudy Slaiby
            Product Manager, Jira Data Center
            {panel}


            {panel:title=Atlassian Update – 15 February 2018|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
            Hi everyone,

            Thanks for your interest in this issue.
             This request is considered a potential addition to our longer-term roadmap.

            We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

            For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:
             * Performance and stability improvements
             * Archiving projects for improved performance
             * Optimising the use of custom fields
             * Improving performance of boards
             * Improving Jira notifications
             * Allowing users to edit shared filters and dashboards
             * Mobile app for Jira Server

            You can learn more about our [approach to highly voted server suggestions here|https://community.atlassian.com/t5/Jira-articles/A-renewed-approach-to-highly-voted-Server-suggestions-for-Jira/ba-p/688117].

            To learn more on how JAC suggestions are reviewed, see our [updated workflow for server feature suggestions|https://community.atlassian.com/t5/Jira-articles/An-updated-workflow-for-Server-feature-suggestions/ba-p/721632#M113].

            Kind regards,
             Jira Server Product Management
            {panel}

            {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-12400].
            {panel}
            JIRA-1100 introduced editable comments. This is great. When our security officer reviewed the feature he wanted access to the change history, which would be important in the event of a security audit. It appears that there is no way to view comment history. I'm opening this improvement request to ask for the ability to view comment change history. Ideally, this would be implemented such that a new permission was added 'View comment change history' so that its implementation could be configured at the site level.             		New: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-12400].
            {panel
            h3. Problem Definition
            JIRA-1100 introduced editable comments. This is great. When our security officer reviewed the feature he wanted access to the change history, which would be important in the event of a security audit. It appears that there is no way to view comment history.

            h3. Suggested Solution
            The ability to view comment change history. Ideally, this would be implemented such that a new permission was added 'View comment change history' so that its implementation could be configured at the site level.
            Andriy Yakovlev [Atlassian] made changes -
            Current Status New: {panel:title=Atlassian Update - 17th of October  2024|borderStyle=solid|borderColor=#2684ff|titleBGColor=#2684ff|bgColor=#ffffff}
            Hi everyone,

            Thank you for your suggestion and for taking the time to share your thoughts with us. After careful consideration, we have decided not to proceed with this feature request at this time.

            We’re currently focusing on other areas of the product and prioritize those that provide the most value to the majority of our users that includes Performance and Scale and Security updates.

            Please remember that [jira.atlassian.com] is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira DC roadmap and the Atlassian DC release notes blog.

            We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.

            Rudy Slaiby
            Product Manager, Jira Data Center
            {panel}

            Sascha.Pfengler added a comment -

            To me this seems like another case of: Do not offer core features -> Thrive on plugin subscriptions.

            Sascha.Pfengler added a comment - To me this seems like another case of: Do not offer core features -> Thrive on plugin subscriptions.

            Gaëtan Mougel added a comment -

            This is an audit log flaw (could change a comment saying "im okay with it" to "over my dead body" without any trail other than "has been changed")

            Todays decision by Atlassian to ignore this issue despite it being easy to fix is extremely disapointing.

            Not to mention that this ticket has been open for 17 years and has the support of 759 voters (assuming an average licence of 1000 users, 759'000 users affected and 58-129Mn in licencing fees alone (software - JSM) + the cut Atlassian takes on marketplace plugins.

            The literal billions of dollars spent by the 759 voters here over the last 17years should get us a developer for 3 days to add history to comments on Jira or Atlassian buying off one of the plugins that solves this audit trail issue and incoporating it.

            Gaëtan Mougel added a comment - This is an audit log flaw (could change a comment saying "im okay with it" to "over my dead body" without any trail other than "has been changed") Todays decision by Atlassian to ignore this issue despite it being easy to fix is extremely disapointing. Not to mention that this ticket has been open for 17 years and has the support of 759 voters (assuming an average licence of 1000 users, 759'000 users affected and 58-129Mn in licencing fees alone (software - JSM) + the cut Atlassian takes on marketplace plugins. The literal billions of dollars spent by the 759 voters here over the last 17years should get us a developer for 3 days to add history to comments on Jira or Atlassian buying off one of the plugins that solves this audit trail issue and incoporating it.
            Rudy Slaiby made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Future Consideration [ 11775 ] New: Closed [ 6 ]

              Unassigned Unassigned
              42480ca243e8 Jeff Schnitter
              Votes:
              759 Vote for this issue
              Watchers:
              398 Start watching this issue

                Created:
                Updated:
                Resolved: