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

Incoming Mail Handler does not respect the default priority in Priorities Scheme

    XMLWordPrintable

Details

    Description

      Atlassian Update – 25 May 2023

      Dear Customers,

      Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base.

      To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided lower its priority and to move this issue to our short-term backlog.

      Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

      Best regards

      Roman Kolosovskiy

      Sr.Product Manager

      Issue Summary

      This is reproducible on Data Center: (yes) / (no)

      Steps to Reproduce

      • Created a New Priority Scheme "Priority Schema 1" with the following priorities and set Lowest as (Default) priority: 
        • Highest
        • Medium
        • Lowest(Default)
      • Create "Project1" and associate the "Priority Schema 1" to this project
      • Created a New Mail Handler "Incoming-MH1"
      • Created a Test Account that will be used in creating the ticket via email (outlook)
      • Reorder the Global Priority as the following:
        • Highest
        • Medium
        • Low
        • Lowest
        • High
      • Send 3 emails from the outlook of the test account as the following and observe the behavior :
        • An email with High Priority ---> The issue got created and the priority is correct (Highest)
        • An email with Low Priority ---> The issue got created and the priority is not correct and it set to --->   High (not available)
        • An email with No Priority ---> The issue got created and the priority takes the default priority "Lowest" which is defined in the  " Priority Schema 1"

      Expected Results

      The issue should be created with the default priority defined in the Priorities Scheme.

      Actual Results

      • An email with High Priority ---> The issue got created and the priority is correct (Highest)
      • An email with Low Priority ---> The issue got created and the priority is not correct and it set to --->   High (not available)
      • An email with No Priority ---> The issue got created and the priority takes the default priority "Lowest" which is defined in the  " Priority Schema 1"

      Workaround

      Reorder again the Global Priorities and we set the default priority as the end of the list. 

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              9085749201b4 Shereen Reda
              Votes:
              7 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated: