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

Ability to remove specific information from history and activity Tab

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

      There could be times where some sensitive data could be inadvertently added to an issue in a text format, on a comment, description, or other forms (Fields, etc). For security reasons and due to regulations (GDPR and others), this information needs to be removed from the instance. Although the user can remove the text, the information will still be present on the history and activity tab of the issue.

      Since the history tab can't be disabled (JRACLOUD-67300), Would be useful, and at some point necessary, that the administrators have the ability to remove data from the history or activity tab in case they need to hide sensitive information from the instance. This would also remove the information on the activity stream where users can see all the changes.

            [JRASERVER-69002] Ability to remove specific information from history and activity Tab

            I would be SO nice to be able to delete any desired history line item for any issue.  Atlassian Jira developers we sure would love to have this feature implemented.

            I used to depend on a Server add-on app that also ran on Datacenter. Its no longer available with the ending of Server support: So disappointing.  That add on is named Issue History Item Remover

            https://marketplace.atlassian.com/apps/1219046/issue-history-item-remover?hosting=server&tab=overview

            The last time a user included a sensitive text in a Jira field, I used the Scriptrunner command to delete the ENTIRE history instead of having to delete the whole issue.

            I first edited all the Jira issues replacing the sensitive text with a stream of XX characters.

            Then I removed this Issue's ENTIRE History, so there is no longer any history that show what the original sensitive text was.

            The Scriptrunner script I used to remove this Issue History from these effected issues:

            for these issues:  JM-7211 etc..

            import com.atlassian.jira.issue.IssueManager;
            import com.atlassian.jira.issue.MutableIssue;

            import com.atlassian.jira.component.ComponentAccessor;

            IssueManager im = ComponentAccessor.getIssueManager();
            MutableIssue issue = im.getIssueObject("JM-7211");

            def changeHistoryManager = ComponentAccessor.getChangeHistoryManager()

            changeHistoryManager.removeAllChangeItems(issue)

            Darryl Hahn added a comment - I would be SO nice to be able to delete any desired history line item for any issue.  Atlassian Jira developers we sure would love to have this feature implemented. I used to depend on a Server add-on app that also ran on Datacenter. Its no longer available with the ending of Server support: So disappointing.  That add on is named Issue History Item Remover https://marketplace.atlassian.com/apps/1219046/issue-history-item-remover?hosting=server&tab=overview The last time a user included a sensitive text in a Jira field, I used the Scriptrunner command to delete the ENTIRE history instead of having to delete the whole issue. I first edited all the Jira issues replacing the sensitive text with a stream of XX characters. Then I removed this Issue's ENTIRE History, so there is no longer any history that show what the original sensitive text was. The Scriptrunner script I used to remove this Issue History from these effected issues: for these issues:  JM-7211 etc.. import com.atlassian.jira.issue.IssueManager; import com.atlassian.jira.issue.MutableIssue; import com.atlassian.jira.component.ComponentAccessor; IssueManager im = ComponentAccessor.getIssueManager(); MutableIssue issue = im.getIssueObject("JM-7211"); def changeHistoryManager = ComponentAccessor.getChangeHistoryManager() changeHistoryManager.removeAllChangeItems(issue)

            One of our users uploaded sensitive information to the comments section and I was unable to delete this from the history. Please can you make this a priority to fix. Thanks (Jira DC 9.12.5 LTS).

            We removed the issue altogether and recreated it with no comments!

            Ritesh Singh added a comment - One of our users uploaded sensitive information to the comments section and I was unable to delete this from the history. Please can you make this a priority to fix. Thanks (Jira DC 9.12.5 LTS). We removed the issue altogether and recreated it with no comments!

            +1 this issue. It doesn't seem important until you need it. I can't imagine why admins can't delete specific details from ticket history

            Aleks Lubiejewski added a comment - +1 this issue. It doesn't seem important until you need it. I can't imagine why admins can't delete specific details from ticket history

            Brittney added a comment - - edited

            Any updates on this request? This is a much needed feature.  Some of us work in high security industries and the ability to delete unintentionally shared information is not only vital but a potential security risk.

            Brittney added a comment - - edited Any updates on this request? This is a much needed feature.  Some of us work in high security industries and the ability to delete unintentionally shared information is not only vital but a potential security risk.

            Need this to be added

            Anthony Woolerton added a comment - Need this to be added

            Mattd added a comment -

            Very interested in this as well. Being able to delete selective history for A) a single ticket or B) Multiple tickets, maybe based on time/date, would be extremely useful!

            Mattd added a comment - Very interested in this as well. Being able to delete selective history for A) a single ticket or B) Multiple tickets, maybe based on time/date, would be extremely useful!

            for the PII review, it's great opportunity

            Gonchik Tsymzhitov added a comment - for the PII review, it's great opportunity

            Sandstone added a comment -

            Hi there, 

            Thanks for the partial workaround provided. Recently, we've followed this and advised our user to clone the ticket and delete the original which includes the sensitive information that need to be deleted. 

            However, we'd like to give some feedback that cloning the ticket and deleting the original is not an ideal solution. It affects the reporting and billing; details like time of creation, time of resolution and time of first response are lost and not copied to the new ticket.

            Thank you. 

            Sandstone added a comment - Hi there,  Thanks for the partial workaround provided. Recently, we've followed this and advised our user to clone the ticket and delete the original which includes the sensitive information that need to be deleted.  However, we'd like to give some feedback that cloning the ticket and deleting the original is not an ideal solution. It affects the reporting and billing; details like time of creation, time of resolution and time of first response are lost and not copied to the new ticket. Thank you. 

            Any progress here? Anyone with workaround?

            I simply need to:

            1. Do not write particular events into history
            2. Selectively remove particular event from history

            I am really wondered that Interface ChangeHistoryManager have nothing like .remove() for history entry, even it can list any, even based on user or type :-o 

            Tomáš Vrabec [Core IT] added a comment - Any progress here? Anyone with workaround? I simply need to: Do not write particular events into history Selectively remove particular event from history I am really wondered that Interface ChangeHistoryManager have nothing like .remove() for history entry, even it can list any, even based on user or type :-o 

            This is an absolute must and necessary for Jira to GDPR compliant, where the opposite can give rise to huge fines.

            Morten Høgholm Pedersen added a comment - This is an absolute must and necessary for Jira to GDPR compliant, where the opposite can give rise to huge fines.

              Unassigned Unassigned
              lmenezes Lele (Inactive)
              Votes:
              244 Vote for this issue
              Watchers:
              145 Start watching this issue

                Created:
                Updated: