-
Bug
-
Resolution: Fixed
-
Low
-
3.29.0, 3.29.1, 3.29.2, 3.29.4
-
2
-
Severity 3 - Minor
-
0
-
Summary
When there is no change to the Parent link or Team field (new value is same as old value), the issue history is still tracking this information like a value change with every single change to any other issue field.
Steps to Reproduce
- Open an issue in Jira with Parent link and Team fields showing up on issue view and edit screens
- Set the Parent link value to point to another issue
- Notice the issue history tracks this change
- Set the Team value
- Notice the issue history tracks this change
- Edit the issue and change another field such as priority, description, ...
Expected Results
Issue history should only track the new change made
Actual Results
Issue history logs the change to the field along with Team and Parent link and display unchanged values.
Notes
Along with recording a change for Parent Link, "issuelink_deleted" and "issuelink_created" events are fired because the issue link for the parent issue is indeed removed and recreated. This may needlessly cause automations to fire.
LOG: execute <unnamed>: DELETE FROM public.issuelink WHERE ID=$1 DETAIL: parameters: $1 = '10705' ... LOG: execute <unnamed>: INSERT INTO public.issuelink (ID, LINKTYPE, SOURCE, DESTINATION, SEQUENCE) VALUES ($1, $2, $3, $4, $5) DETAIL: parameters: $1 = '10706', $2 = '10300', $3 = '10501', $4 = '10800', $5 = NULL
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
