This story apply on following fields:

• submitted_by
• last_update_by
• assigned_to

The 2 firsts are "Always There Fields" while the later is defined by semantic. Specificities of ATF are described in the epic.

For those fields:

• Can use =, !=, IN, NOT IN operators
• None and '' (empty string) should be taken into account (same behaviour than on single tracker)
• Can use MYSELF() function
• Search is done on username
• Field/semantic must be readable in all trackers of query

For "assigned_to" semantic:

• In single-tracker TQL search, given a list field is bound to a user group, for example 'Project Members', when I search a username 'johndoe' and 'johndoe' is not a 'Project member', then an error is shown to tell me that 'johndoe' is not a valid value for this field.
• In cross-tracker TQL search, that check is not made. Searching on 'johndoe' will yield 0 results because 'johndoe' is not a 'Project member'