Hide or edit issue history

We have an issue in our JIRA where a fairly large number of issues were created that had information about projects in our operational deployments. These deployments are covered by HIPAA privacy rules, which means we need to have any specific information in a project that's not publicly accessible.

Going forward this is easy: we have a project specific to our operational deployment that isn't publicly accessible. Any issues in our platform code that need to reference information about an operational deployment gets two issues: one describing the problem in a generic way in the publicly accessible project and one with the data particular to our operational deployment in the non-accessible project.

The problem we have is our existing issues for operational deployments in the publicly accessible repo. We can modify the publicly accessible issues to remove the sensitive data and create new non-accessible issues, so that we're just creating the same scheme we want to use for new issues. The problem is that all of the sensitive data remains in the publicly accessible issue through the history tab, rendering the whole exercise moot for existing issues.

Going forward, there are only two options I can see:

  • Make the issues in the publicly accessible repo with sensitive information inaccessible to users outside of our development group (this is probably not great, given that it relies on people not later on unhiding the issues)
  • Hide or modify issue history in our publicly accessible repo so that either any sensitive info can't be seen by people who don't have the appropriate permissions or that the sensitive info is actually just removed by having edited or removed the relevant chunks of issue history

Any help on this would be greatly appreciated. It's a critical issue for us in terms of getting our repository suitable for public access.

1 answer

1 accepted

1 vote
Accepted answer

Yes, you can. Its always risky to do this type of stuff, and youll wanrt to be sure you backup first.

You should be able to manipulater 3/4 tables in the DB related to change history.


Or (although I never tried this method) you could use a plugin or grovvy scripts to access the ChangeHistoryManager to purge _all history_


Make sure JIRA is shutdown, backed up, and reindexed immediately after the changes.

I was really hoping for something more direct through the web interface, since it seems like this is a scenario that has a better than 0% chance of occurring :) Oh well, we're already going to be delving into the internals of Crowd and some other tools to disentangle ourselves from our department's AD server, might as well get our hands dirtier while we're at it. Thanks for the help!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,731 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you