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.

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      We have a long-running project, where some of the components are no longer relevant (e.g. they were archived, merged, or discarded).
      However, we prefer not to delete these components, since we might still need to relate to their corresponding issues.
      Hence, we would like to have a way to mark such components as 'obsolete'. This means that:

      • they won't be available in the 'Components' field when creating an issue (perhaps also when updating an existing issue).
      • they will be available when filtering.
      • they will appear separately (or struck-through) in the Components tab of the project.

            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.

              • Icon: Suggestion Suggestion
              • Resolution: Duplicate
              • None
              • None
              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

                We have a long-running project, where some of the components are no longer relevant (e.g. they were archived, merged, or discarded).
                However, we prefer not to delete these components, since we might still need to relate to their corresponding issues.
                Hence, we would like to have a way to mark such components as 'obsolete'. This means that:

                • they won't be available in the 'Components' field when creating an issue (perhaps also when updating an existing issue).
                • they will be available when filtering.
                • they will appear separately (or struck-through) in the Components tab of the project.

                        Unassigned Unassigned
                        0e91e160c154 Yossi Zinger
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            0e91e160c154 Yossi Zinger
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            1 Start watching this issue

                              Created:
                              Updated:
                              Resolved: