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

CreateOrCommentHandler should have parameter for priority

XMLWordPrintable

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

      Creating an issue via email works great for us.

      Due to some persons use of emails (sending them with high priority regardless of content) they always end up in jira as blocker. Because of the political implications of "downprioritizing" an issue, we usually don't do this, but it really screws up our statistics. I'd rather prioritize some initially "normal" support request up to blocker, thus I'd like the CreateOrCommentHandler to offer a parameter for the standard priority. It could and should still default to the current behaviour, if this parameter is not given.

            [JRASERVER-10558] CreateOrCommentHandler should have parameter for priority

            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

            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

            GULP Admin added a comment -

            As this feature is already present in JIRA, it should also be configurable without having to install an add-on.
            So the best thing would be to have a dropdown menu, where one can select the default issue priority for high priority emails or disable this feature.

            GULP Admin added a comment - As this feature is already present in JIRA, it should also be configurable without having to install an add-on. So the best thing would be to have a dropdown menu, where one can select the default issue priority for high priority emails or disable this feature.

            Andy Brook (Javahollic Software) added a comment -

            And also, there is a free solution JEMH , you can set a default priority, but override on a per-email basis through directives in the subject "#priority=low" or in the first line of the body "@priority=low"...

            Andy Brook (Javahollic Software) added a comment - And also, there is a free solution JEMH , you can set a default priority, but override on a per-email basis through directives in the subject "#priority=low" or in the first line of the body "@priority=low"...

            Bogdan Dziedzic [Atlassian] added a comment -

            Just to let you know, there is a commercial solution at http://www.softwaretesting.de/jira/artikel/pix-email-handler.html that may suite your needs.

            Cheers,
            Bogi

            Bogdan Dziedzic [Atlassian] added a comment - Just to let you know, there is a commercial solution at http://www.softwaretesting.de/jira/artikel/pix-email-handler.html that may suite your needs. Cheers, Bogi

            Brian Pedersen added a comment -

            If there was a way to allow for mapping the X-Priority header property to a Jira priority for CreateOrCommentHandler's, this would be great. We are having the same issue with emails coming in as high priority and being created as blocker priority in Jira.

            Brian Pedersen added a comment - If there was a way to allow for mapping the X-Priority header property to a Jira priority for CreateOrCommentHandler's, this would be great. We are having the same issue with emails coming in as high priority and being created as blocker priority in Jira.

              Unassigned Unassigned
              4517beae0e65 Olaf Kock
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: