Details
-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.29.2, 3.29.4, 3.29.6
-
None
-
2
-
Severity 3 - Minor
-
Description
Issue Summary
When a subtask gets created after the parent issue gets associated with Team, the plan will not show the subtask on its board and JQL searches.
Steps to Reproduce
- Create parent issue ABC-1 > associate with Team value (Team1)
- Create subtask under ABC-1, lets say issue key = ABC-2
- Check a board where the ABC-1 is on
- Search for the issue with a JQL using the Team value, e.g:
project = ABC and team = Team1
Expected Results
The board/JQL will show the ABC-2 sub-task
Actual Results
The board/JQL is just showing the ABC-1 issue
Workaround
Seems to be breaking the index, so user can:
- Run project reindexing, OR
- Remove and re-add the team value for parent issue ABC-1 on the plan, then apply the changes back to Jira via Review changes
Attachments
Issue Links
- is related 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
-
JPOSERVER-2748 Modifying a Sub-tasks team field from Software Boards cause inconsistencies
- Closed
-
JPOSERVER-2931 Plan doesn't show Team field value for subtasks created after its parent is associated with Team intermittently
- Closed