Details
-
Suggestion
-
Resolution: Fixed
-
Firefox, Windows XP Pro
-
627
-
10
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thank you for your votes and thoughts on this issue.
We fully understand that many of you are dependent on this functionality.
After careful consideration, we've decided to prioritize archiving components on Jira Server roadmap. We hope to start development after our current projects are completed.
Expect to hear an update on our progress within the next 6 months.
To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.
Kind regards,
Jira Server Product Management
Original request description
I use the project components very heavily for issue list filtering and rely on them for building out lists in Confluence using the
{jiraissue}macro.
In order to preserve those lists, I have to keep the component around, unfortunately, many times I don't necessarily need it for future work. So I don't want to present the developers with the component if it doesn't really apply to work anymore.
It would be great if there was a mechanism to "archive" components just like you would with a release version, such that the user can no longer select that component for issues.
Attachments
Issue Links
- causes
-
JRASERVER-71601 Deleting archived component leaves orphan issue association
-
- Gathering Impact
-
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is incorporated by
-
- Closed
- is related to
-
- Closed
-
- Future Consideration
- relates to
-
- Gathering Interest
- is resolved by
-
PC-8535 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
