Mapping a new priority under priority scheme does't reflect in issue history

XMLWordPrintable

    • 2
    • Severity 3 - Minor

      Issue Summary

      While making changes in priority scheme lets say if you map a new priority from Priority A  --> Priority B, ideally we would expect that in issue history this gets recorded however currently this is not captured and so there is no where to know if the priority was remapped.

      Steps to Reproduce

      1. Login into the site
      2. Go to settings -> Priority schemes 
      3. Add a new or delete a priority and then map it to the appropriate priority.
      4. Notice that there wouldn't be any record in the issue history for this update.

      Expected Results

      Ideally if a new priority is mapped that should get recorded in the issue history.

      Actual Results

      Currently nothing is recorded for this event/change.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Kushal Desai
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: