We have been running a project for a very long and now want to clean up the project. Some of the parts of the project that have become irrelevant are:
It is not the best experience to still see these components, issue types and labels appear although they are not in use anymore.
The easiest way to go about them would be to delete the irrelevant ones but that would mean:
Any way I can achieve this goal?
A few options to ponder:
Regardless of what solution you choose, remember to check the following for impacts: automation rules, Confluence macros, dashboards, reports, etc.
I prefer not to delete issues also (to the point of disabling that permission globally). Usually I find that just closing issues makes them "go away" well enough, at the expense of looking at them for a week or so in the Done column.
Let us know what you decided to do, and how it worked for you!
Good point @Mykenna Cepek .
@Nischal Sharma Deleting old issues certainly gives you no future access to analyse them.
Options 1, 2, and 4 may not require Jira admin permissions as these can be done by someone with project permissions.
The idea of creating new projects may be frowned upon in some organisations as this creates addition setup & cleanup work too.
If you decide to go ahead with any option, an additional action item should be to review how you use components and labels across your teams - and see if you can establish a better practice that ill make issue management less of an hassle in future.
Let us know how it goes.
One approach could be to create a catch-all, "no-release" release (Fix Version) and assign all issues that do not fit anywhere else. This way you do not need to worry about the issue status, component, etc., and if any issue is discovered later to be of any significance, it could be moved out of the "no-release" bucket.