• 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.

      Right now, issue types and priorities are merely a lable, a description and an icon. I would like to see something much more useful.

      Part of this is because I expect to modify the workflows to encapsulate our business processes to the greatest extent possible by JIRA and what I can con our "Powers That Be" into letting me do.

      I would like to be able to assign different work flows to different types of issues.

      For instance, our feature requests have to be prioritized by a specific committee (at least major feature requests) so the workflow for feature requests will need to go through a workflow that takes it through that committee processes where it will be prioritized and scheduled and so on before being sent to development.

      In addition each issue type needs to have a diferent set of information. A good example of this is with the current setup. I think that for the most part the environment is not meaningful for new features. If I'm going to have different workflows for each issue type, I'm going to need different data to run those workflows.

      I would also like to have different priority sets for each type of issue.

      I think it would also be useful to establish who can create which types of issue (as a member of the public, I should never be able to create a task, for instance) and also which priorities they are able to set. It possible that I only want certain people to set the priority to certain values (for instance the "Oh no! Fix this now or the whole company is going into the toilet" priority should probably only be set by Managers).

            [JRACLOUD-3509] Extend Issues Type and Priority behaviour

            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

              Unassigned Unassigned
              97698cd5ee32 Adam van den Hoven
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: