Updating a sub-task from the edit screen with the JPO Teams field exposed and inherited from Parent removes the Team

Issue Summary

If you update/edit a sub-task while the Teams field is added to the edit issue screen, the system will remove the inherited team from the sub task, BUT will leave the Team within the UI. If you then reindex the instance, when you search by Team in the UI, the sub-tasks do not appear even though the Team remains in the UI of the issue. This does take a specific series of steps described below.

Steps to Reproduce

1. Create Parent and sub task within a JPO Plan
2. Create Shared Team
3. Add Shared Team to Parent issue (sub-task will inherit it)
4. Within issue source/project, add Teams field to the edit issue screen
5. Edit the sub-task, make no changes, and click update
6. Observe issue history showing Team field has changed from selected Team to Empty
7. Full Lock and Reindex the instance
8. Search for issues by Team
9. Observe Sub-task that was updated does not appear, but keeps the Team in the Teams field of the Issue View

Expected Results

Updating a sub-task with the Team field exposed would not change the inherited Team.

Actual Results

Sub-task will retain the value in the Teams field, but appears to be out of sync with the index. This causes the sub-tasks to not appear in searches or in Boards that filter by Team Id.

Workaround

Remove Team field from edit issue screen.

NOTES: Further testing appears to show that this can occur even when the field is not exposed on the edit issue screen. You can cause this just by updating the issue when the Team field appears on the issue view screen.