Summary
When a subtask gets created after the parent issue gets associated with Team, the plan will not show the subtask has inherited Team value from its Parent. This is reproducible intermittently.
Steps to reproduce
- Create parent issue ABC-1 > associate with Team value
- Create subtask under ABC 1, lets say issue key = ABC-2
- Refresh the plan
Expected result
The plan will show ABC-2 (subtask) has Team field value same as its parent's team field value
Actual Result
Workaround
Workaround 1
Seems to be breaking the index, so user can:
- Run project reindexing, OR
- Remove and readd the team value for parent issue ABC-1 on the plan, then apply the changes back to Jira via Review changes
Workaround 2
- Add this system property to disable filtering indexers by value ( Setting properties and options on startup )
-Djira.cfv.driven.indexing.disabled=true
You can learn more about this property from Optimizing custom fields
- Restart Jira
- Perform a full re-index.
- is related to
-
JSWSERVER-20867 Background or project re-index changes for Team Field for subtask is not replicated to other nodes
- Closed
- relates to
-
JPOSERVER-2948 Viewing a Subtask while DVCS accounts are synced(Or any non-interactive indexing ) causes Advanced Roadmaps Team custom field to be dropped from indexes
- Closed
-
JPOSERVER-2971 Team field value for subtasks created after its parent is associated with Team intermittently
- Closed
- derives
-
JPO-16378 Loading...
- is caused by
-
FLASH-2030 Loading...