Delete logs and attachment from jira tickets
Asked by khaoula_dachraoui:

Hello

Do you have any idea how we can delete all logs and attachments from all Jira tickets for a period of 2 years.

Thank you

Regards


Answers:
author: Trudy Claspill
body: Hello [@khaoula_dachraoui](/t5/user/viewprofilepage/user-id/4664188)

How does the 2 years apply in this scenario?

* Does that apply to the creation date of the issues?
* Does it apply to the date the issue was Resolved?
* Does it apply to the date the issue was last updated?
* Does it apply to the date the attachment was added to the issue?

What exactly are you referring to by "logs"? Are you talking about time tracking Work Logs? Are you talking about the history log of changes to the issue?

Can you tell us more about the problem you are trying to solve? There may be a better solution than deleting the data. And be advised that if you do delete data, it will be permanently deleted with no option to recover it at a later date.

comments: author: khaoula_dachraoui
body: Hello [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

Thank you for your reply!

As an admin, I need the ability to define the sensitive, confidential, or proprietary information that needs to be removed (exfiltrated) from our Atlassian cloud instances and execute the removal, so that I can effectively meet the compliance and governance requirements of our business.

So i thought it would be good if i can apply this scenario to a closed ticket .

We need to delete all the attachments (logs coming from the clients , use case attached as word, excel spreadsheet with personal information data etc ....).

Do you think can we set up a rule or using script is better?

Thanks

Regards


author: Trudy Claspill
body: Hello [@khaoula_dachraoui](/t5/user/viewprofilepage/user-id/4664188)

Thank you for the additional information.

With Automation rules you can select issues based on the Resolved date (if that is the same in your environment to when you would consider the issue "closed"). You can then execute an action in the rule to Delete Attachments for each issue selected.

You can delete all attachments or use a "matches" or "does not match" condition with a regex to specify the attachments to be deleted.

![Screenshot 2024-07-24 at 2.50.08?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/337753i8480D4220D585268/image-size/large?v=v2&px=999 "Screenshot 2024-07-24 at 2.50.08?PM.png")

You could run such a rule on a schedule to find all the issue that have "newly" entered the range of having been closed for 2 years.

What is the current count of issues that have been closed for 2 years or longer for which the attachments need to be deleted? There are limits to how many issues can be processed in the run of a rule, so dealing with a backlog may require running a rule multiple times.

Once again I have to stress that if you use the above action the attachments are **permanently deleted**. There is no "undo" option if you make a mistake, and there attachments are not moved to a "trash" bin from which they can be recovered. The are irrevocably gone. So, if you created an automation rule such as this I would very strongly caution you to do testing of the rule where you don't actually include the Delete Attachments action. Instead use the Log Action to write to the rule execution audit log what issues would be affected, and maybe even write information about the attachments that would be deleted.

Information about Automation Rules and how to construct them can be found here:

<https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/>

If you have more questions or need more clarification, don't hesitate to ask.


author: khaoula_dachraoui
body: Hello [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

Thank you very much for these details.

Nice day

Khaoula


author: Trudy Claspill
body: You're welcome!

If my responses ultimately provide you with a working solution for your requirement, please consider clicking on the Accept Answer button to mark your Question as Solved.


Tags: cloud

jira-cloud

not-applicable

security-and-access-policies