Issue Summary
Unable to set ownerId on Tasks endpoint with POST or PATCH calls
Currently, these are the responses:
HTTP 400
Cannot create task. ownerId doesn't belong to the same team as storyIdHTTP 400
Cannot update task with id <id>. ownerId doesn't belong to the same team as storyId
Steps to Reproduce
Validated the following scenarios via UI:
Scenario: Story has NO related Agile team
Method #1 – Add via Quick Add section within Story slide-out panel
Task Owner can be selected among the team members of the following teams: any teams related to the Program (the Program team itself + any other Agile or Kanban team)
Method #2 – Via Task grid page
Same as above + the current user
Scenario: Story HAS one related Agile team
Method #1 – via Quick Add section within Story slide-out panel
same as previous scenario Task Owner can be selected among the team members of the following teams: any teams related to the Program (the Program team itself + any other Agile or Kanban team)
Method #2 – Via Task grid page
Once Story is selected, Task Owner can be selected among the associated Agile team members + the current user notice Program team members are no longer allowed as explicit Agile team has been assigned
Expected Results
- API should mirror the minimum validation presented in the UI.
The Task Owner must be a member of Program Team or Agile Team associated to the respective Story.
The relationship chain is like:
- Program (Program Team) >> Agile Team >> Story >> Task
So before trying to select an Owner for a Task you must validate that user's membership to some of those teams.
Actual Results
- API returns 40x:
HTTP 400
Cannot create task. ownerId doesn't belong to the same team as storyIdHTTP 400
Cannot update task with id <id>. ownerId doesn't belong to the same team as storyId
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- resolves
-
ALIGNSP-3992 Loading...