Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-4504

Would like issue types scoped at the Project and Project Category level

    • 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 would like to have issue types assigned to a project category, so that only specific projects or projects within a specific Project Category have access to an issue type.

            [JRASERVER-4504] Would like issue types scoped at the Project and Project Category level

            Hi,

            While we won't be implementing this directly, we are making changes to the administration section around projects and issue types that will make this much easier.

            Regards
            Josh

            Josh Devenny added a comment - Hi, While we won't be implementing this directly, we are making changes to the administration section around projects and issue types that will make this much easier. Regards Josh

            Aviva added a comment -

            This is absolutely still relevant.
            All things should be configurable at the project category level. Fields, Screens schemes, field configurations, workflows, etc.

            For instance, when I need change a workflow scheme, permission scheme, etc... I need to adjust it for all 50 relevant projects in one project category. The division is already there and searchable. Why isn't it used for configuration as well?

            Aviva added a comment - This is absolutely still relevant. All things should be configurable at the project category level. Fields, Screens schemes, field configurations, workflows, etc. For instance, when I need change a workflow scheme, permission scheme, etc... I need to adjust it for all 50 relevant projects in one project category. The division is already there and searchable. Why isn't it used for configuration as well?

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Josh Devenny and Roy Krishna
            JIRA Product Management

            Josh Devenny added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Josh Devenny and Roy Krishna JIRA Product Management

            AvivaY added a comment -

            Why is there no activity on this issue? I don't see a solution....

            -Aviva

            AvivaY added a comment - Why is there no activity on this issue? I don't see a solution.... -Aviva

            This is a definite need for our organization. We have considered splitting up our Jira instance just to minimize the number of issue types as we have multiple business units that only desire to see the custom issue types related to their project.

            Currently however, we do not have a company wide active directory for authentication, and many of our current jira users would have to reside in both instances of Jira so that solution is not very feasible to us.

            Matt Vanchura added a comment - This is a definite need for our organization. We have considered splitting up our Jira instance just to minimize the number of issue types as we have multiple business units that only desire to see the custom issue types related to their project. Currently however, we do not have a company wide active directory for authentication, and many of our current jira users would have to reside in both instances of Jira so that solution is not very feasible to us.

              Unassigned Unassigned
              a8455a07a4ec Robert Castaneda[ServiceRocket]
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: