Issue Summary
When removing endSprintID field of a Feature through API PATCH the field startSprintID is removed as well
This is reproducible on Data Center: yes
Steps to Reproduce
- Create Feature in JA
- Enable toggle for TargetSprint fields in Admintration > Settings > Details Panel Settings
- Go to the Feature and update Target Start and Target Completion fields
- Update to null the endSprintID field on the Feature through API using PATCH.
- startSprintID will set to null as well.
Expected Results
startSprintID not be allowed to be removed unless endSprintID is also removed (both values must be null or both must be populated, else throw an error)
Actual Results
Users dont know we're automatically removing one of the values of the other is removed
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JIRAALIGN-4500 Deleting Anchor Sprint from PI removes data from UI but does not delete from backend
-
- Closed
-
-
JIRAALIGN-4503 When updating endSprintID field of a Feature through API nothing is being logged in Audit Log of the Feature
-
- Closed
-