Issue Summary

JQL search is not validating the context for team-managed fields, therefore a JQL search can return unexpected results from invalid contexts.

This is an edge case dependent on Moving work item between team-managed projects keeps values for project-specific fields for the original project

Steps to Reproduce

1. Move a work item as described in the bug report linked above; due to the duplicated fields, the work item ends with two values for the same field
2. make a JQL query to based on the content of the custom field

Expected Results

Only the context for the current project of the field should be considered

Actual Results

All results are shown, for example:

Workaround

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