-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 11.22.0
-
Component/s: Obstacles - Dependencies
-
None
-
1
-
Severity 2 - Major
-
No
-
None
Issue Summary
Dependency > Owner field is wiped out when updating other fields via API, and there is no trace of this in the Dependency Audit log
A dependency object is missing the "owner" field in JA REST API, which exists in the UI and can be populated in UI.
Any Patch API request user makes to modify/update any other fields of a dependency will clear the owner field out without a trace in the audit log.
Steps to Reproduce
- Have a dependency that has the Owner field populated in the UI
- Update the dependency via JA REST API Patch call, changing some other field , example: title
- After the above Patch update, check the dependency in the UI
- Notice the owner field is blank
- Check the dependency audit log, we can see the other field was updated via API, which is fine.
- However, there is no trace in the audit log of this owner field being wiped out via the API.
Expected Results
Dependency > Owner field that was populated in the UI, should not be wiped out when updating other fields via API
Actual Results
Dependency > Owner field is wiped out when updating other fields via API, and there is no trace of this in the Dependency Audit log.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- blocks
-
PS-192756 Loading...
- consists of
-
JAROT-1534 Loading...