We need to be able to archive components when they are "retired", but we still need to be able to track those tickets by component.
I found 2 okay solutions, but would like to have a better one.
Option 1: rename the component to something like "component-archived"
Option 2: create a custom field called something like "Inactive component" and copy the component into it on every ticket. Then delete the component.
These are clunky and not great. We would love to have a better solution to this.
I am aware of https://jira.atlassian.com/browse/JRACLOUD-10507 but need a solution in the meantime.
Hello @Paul Madison,
Thank you for reaching out to Atlassian Community!
Checking the feature request and similar cases, I’m afraid to say that there are no other workarounds for that.
The only other one I found is related to archiving projects, where the components would also be archived, but this feature is only available for Jira Software projects.
Also, I’ve checked internally but there are no updates regarding the feature as well.
Please, vote and also watch the ticket to receive updates from our product managers. When they have updates, they will post them on the description of the ticket.
Kind regards,
Angélica
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.