Summary: Modifying a Sub-tasks team field from Software Boards cause inconsistencies
Steps to replicate:
- Create a kanban board that filters by team;
- Give an user permissions to edit issues in the project
- Revoke permissions to commit to plans (Plan Permissions > Edit plan);
- Create a Story and assign the this board's team to it;
- Commit the changes in JPO;
- Create a sub-task after assigning the team to its parent's;
- * Note that the team field is empty for the sub-task;
- Expand the issue detail view for the parent task and scroll down to subtasks, note the message saying "1 sub-task is being filtered by the board's Saved Filter"
- Access the children task and re-assign it to the correct team;#
- * Note that it shows up in the board
- Make any changes that would reindex the sub-task (or trigger a locked reindex)
Expected results:
- The sub-task keeps its assignment of the team
- Or the sub-task pulls the team information from its parent (since JPO rolls the value down to sub-tasks)
Actual results:
The sub-task loses the parent value and the sub-task is once more filtered from the board.
Workaround:
Re-assign the team from the Plan view and commit the changes in Portfolio instead.
- relates to
-
JPOSERVER-2729 Updating a sub-task from the edit screen with the JPO Teams field exposed and inherited from Parent removes the Team
-
- Closed
-
-
-
- Closed
-
-
JPOS-4831 You do not have permission to view this issue
[JPOSERVER-2748] Modifying a Sub-tasks team field from Software Boards cause inconsistencies
We are seeing this issue occur when not only editing subtask tickets, but also transitioning their state within the kanban board. The workaround is entirely unintuitive and frustrating to the team in those cases.
Closing this issue as believe it has been fixed with the 3.21 release