-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
11.13.1
-
1
-
Severity 3 - Minor
-
No
Issue Summary
If a user changes the type of a parent Goal to a type where it can no longer be a parent, the child Goals retain and report the former parent goal's ID in the API and Enterprise Insights as their current parent ID.
This also causes duplicate entries of the child in the OKR tree.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Create a Goal as the Long Term Strategy type. (Goal A)
- Create a Goal as the Core Value type. (Goal B)
- Set Goal B as a parent of Goal A.
- Change Goal B's type to Long Term Strategy and save.
- Perform a GET with the API on Goal A or look at Goal A's Parent ID in Enterprise Insights.
- Check the OKR Tree in Strategy Room.
Expected Results
Goal A's parent ID is set to '0', identifying it as an orphan in reports.
Actual Results
Goal A retain the parent Goal B's ID.
OKR tree display duplicate entires of Goal A.
Workaround
Manually opening each child goal and saving it without selecting a new parent will reset the Parent ID to 0 as expected.
- relates to
-
JIRAALIGN-4924 Changing the level of a parent Goal leaves parent goal ID in children.
-
- Closed
-
- causes
-
ALIGNSP-29704 Loading...
- is connected to
-
JAVOM-6978 Loading...