Summary: Modifying a Sub-tasks team field from Software Boards cause inconsistencies

Steps to replicate:

1. Create a kanban board that filters by team;
2. Give an user permissions to edit issues in the project
3. Revoke permissions to commit to plans (Plan Permissions > Edit plan);
4. Create a Story and assign the this board's team to it;
5. Commit the changes in JPO;
6. Create a sub-task after assigning the team to its parent's;
7. * Note that the team field is empty for the sub-task;
8. 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"
9. Access the children task and re-assign it to the correct team;#
10. * Note that it shows up in the board
11. Make any changes that would reindex the sub-task (or trigger a locked reindex)

Expected results:

1. The sub-task keeps its assignment of the team
2. 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.