Follow-up of story #38263. List fields (selectbox, radio button, checkbox, multi-selectbox, openlists) are added to the supported fields for SELECT keyword. Only lists with the same type of binding are compatible:

• lists bound to static values (for example Status) are compatible together, but are NOT compatible with lists bound to users or to user groups
• lists bound to users are compatible together, but are NOT compatible with lists bound to static values or to user groups
• lists bound to user groups are compatible together, but are NOT compatible with lists bound to static values or to users.

Other duck-typing rules (related to permissions, absence of field in a given tracker, etc.) defined in story #38263 also apply to lists.

Lists bound to static values can optionally have a color bound to static values. For example, a list field called "Status" might have values like "Ongoing", "In review", "Done". "Ongoing" value can have the "neon-green" color, "In review" the "clockwork-orange" color and "Done" the "inca-silver" color. Other "legacy" colors have existed throughout the history of Tuleap, where you could choose any RGB combination (for example Red 255, Green 0 and Blue 0).

Given I have selected (using SELECT TQL keyword) a field called "status", and the field values have "legacy RGB" colors assigned, and there is an artifact of this tracker with the "Ongoing" status that matches the TQL query, when the cross-tracker search widget shows this artifact, then there will NOT be any color badge for the "Ongoing" status. It will display as if it didn't have any color assigned.

This choice is made to promote usage of the "new" color palette for Tracker list fields, with color names like "neon-green".

Figma mockup: https://www.figma.com/design/oDjT4tC3fDGP5P4JdKfkdE/Columns-choices---ST?node-id=67-21319