We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 689
    • 57
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 4 January 2016

      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.

      Workarounds

      See comment here

       

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 689
              • 57
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

                Atlassian Update – 4 January 2016

                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.

                Workarounds

                See comment here

                 

                        Unassigned Unassigned
                        f983a72c130d Aaron Godert
                        Votes:
                        1064 Vote for this issue
                        Watchers:
                        520 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            f983a72c130d Aaron Godert
                            Votes:
                            1064 Vote for this issue
                            Watchers:
                            520 Start watching this issue

                              Created:
                              Updated: