Details
-
Suggestion
-
Resolution: Unresolved
-
Firefox, Windows XP Pro
-
959
-
36
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.
Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
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.
See comment here
Attachments
Issue Links
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
- is incorporated by
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
