Hi everyone,

Thank you for your feedback on this suggestion. I understand the importance of addressing scenarios where sensitive data might inadvertently appear in issue history, especially given security and regulatory requirements like GDPR.

Currently, the only way to remove issue history is to clone the issue and delete the original. While this workaround is functional, we recognise that it is not ideal or convenient for most use cases.

I’m excited to share that, as part of the Atlassian Guard Premium offering, we are working on the ability to redact sensitive data from both the issue and its history. This feature is planned for release in the first half of next year.

Thank you again for your continued input and patience. Please feel free to reach out with any further questions or feedback.

Best regards,
Ahmud
Product Manager-Issue View 

Hi everyone,

Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future. Issue History is designed for audit and traceability, at this point in time we will not be looking to change this decision.

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 Cloud roadmap and the Atlassian Cloud 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.

Ahmud
Product Manager-Issue View