-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 11.10.1
-
Component/s: Dynamic Reports - Backlog
-
1
-
Severity 2 - Major
-
No
Issue Summary
When work items are moved from an active process step to Unassigned in Backlog - Kanban - Process Flow view, the ProcessStepID is set to 0, which is an invalid step. Efforts to PATCH the work item will then result in an invalid ProcessStepID error because ProcessStepID is not included in the Process Flow.
Steps to Reproduce
- Apply a Process Flow
- Navigate to Backlog > Capabilities Backlog > Kanban - Process Flow View
- Move the Capability to any Process Step other than Unassigned in the Backlog
- Move the Capability back to Unassigned
- GET on the Capability will return 0 for processStepId field
- PATCH on the Capability for any field returns invalid processStepId error
Expected Results
Process Step ID 0 is excluded from API validations
Actual Results
API PATCH calls fail with processStepId = 0 because that step cannot be included in any Process Flow
Workaround
Move the work item to any other Process Step in the Kanban view, or assign it a Process Step in the Details tab.