Hi All,
Does anyone here have data retention policies they implement in Jira? If so, how do you implement these? I would love to hear what others are doing.
Thanks for the info @Mykenna Cepek
The why is for a few combinations of things. One driver is that we've been operating on a Jira instance for >8 years, so the unneeded "cruft" has built up. (We don't need to save the fact that Jenny requested a new laptop back in 2013)
We've been exploring a retention policy to help clean things up and remove legacy unneeded data. We're looking at an initial sweep of unused projects with a goal of the remaining projects in our instance active, or recently active projects.
From there, implementing blanket retention policy of XX months on issues so that any issue not updated in XX months is deleted.
Thanks for that info. A few further thoughts:
It might be worth deciding whether you really want the hassle of dealing with individual issues. Or instead just wait until an entire project hasn't been touched in N years, and then delete the project. The latter would be much less work, and automation can still help you hunt for them.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Become an effective Jira admin
Manage global settings and shared configurations called schemes to achieve goals more quickly.
Streamline Jira administration with effective governance
Improve how you administer and maintain Jira and minimize clutter for users and administrators.
Learning Path
Become an effective Jira software project admin
Set up software projects and configure tools and agile boards to meet your team's needs.