-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
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
- Login into the site
- Go to settings -> Priority schemes
- Add a new or delete a priority and then map it to the appropriate priority.
- 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
- is related to
-
JRACLOUD-78430 Adding, reordering or removing priority does not log an entry in audit log
- Gathering Interest