-
Bug
-
Resolution: Timed out
-
Low
-
7
-
Severity 3 - Minor
-
Summary
If a resolution is set by both screen and post function, it will not be captured in the issue history
Environment
(Optional - If Applicable)
- Version : 1000.499.4 (Cloud)
Steps to Reproduce
- Configure the Resolve issue transition post function to set the resolution
- Configure the Resolve issue screen to have the resolution screen
- Create an issue and resolve it, make sure to select the resolution field on the screen
Expected Results
Issue history captures the resolution
Actual Results
Issue history does not capture the resolution
Note
- JSD notification will not be sent: JSD-4038
Workaround
Use either one method to set the resolution and avoid using both
- is related to
-
JRACLOUD-65153 Assignee changed not saved in history if the change is made with a post function
-
- Closed
-
- was cloned as
-
JRASERVER-66091 Field update is not captured in issue history if it is set to an equal value through a screen and a post function
-
- Closed
-
- is caused by
-
CRANE-592 Loading...
- mentioned in
-
Page Loading...