I would like to cleanup the available components in a JIRA project. We used components for different situations/reasons, but now we have a clear view what components we would like to use. But, when I delete a component, I suppose that it is also removed from the issues?
My request, I would like to make a few components not visible anymore when I create a new issue, but they should still be linked to the older issues. How should I do this in Jira?
When you delete a component that has related issues, you get the choice whether to remove it from the issues or to swap:
Unfortunately, JIRA doesn't offer a simple way to archive (i.e. prevent selection on create, but still keep on the older/existing issues).
This is the feature request, if you want to vote for it: https://jira.atlassian.com/browse/JRA-10507.
There are a couple of workarounds people have suggested:
There might be other suggestions, but I hope these are helpful.
Thank you for your quick response.
I would like to keep the components that now are linked to the current issues. But, I would like to filter the list of components when I add a new issue.
This way I keep the history of linked components linked to issue and for new issues I would like to have less components available to select.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
As a Jira power user, I was at first doubtful that Trello could benefit my workflow. Jira already uses boards (ones you can customize!), so why would I even need to use Trello?! In this post you will...
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!
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