Issue Summary

Observed this for search key: QueryProjectAnalyserImpl - when issue is a type of subtask.

When searching for issues using the team field, there is inconsistent behavior between JSIS (New Jira Search) and JVIS (Old Jira Search) for subtasks:

• JSIS (New Jira Search): Filters subtasks based on the team field value of the subtask itself.

• JVIS (Old Jira Search): Filters subtasks based on the team field value of the parent issue.

This leads to discrepancies when the team field values differ between a subtask and its parent, or when the parent’s team field is empty.

Steps to Reproduce

1. Create a subtask, add team field value (say x). 
2. Keep a different team field value(say y) for the parent or remove it all together. 
3. We observe additional issues returned when searching with respect to x & missing issue ids when search with respect to y.

Expected Results

Filtering by team should return subtasks only if the parent issue’s team field matches the filter value.

Actual Results

Filtering by team returns subtasks if the subtask’s own team field matches the filter value, regardless of the parent’s team field.

...

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available