Historically I have been able to run JQLs on custom fields with type "Select List (single choice)" in the following way:
But I am now receiving errors and need to include a [dropdown] suffix. This syntax is working without errors:
Can anyone explain why I might now need the [dropdown] suffix? I have soooooo many places with saved queries that if they all need to be updated with [dropdown], its a massive job. Is this something controlled in settings? Has there been a change on the Atlassian side?
Hi Kristin!
I can't really say what's the reason for that change, but tbh I find it pretty useful. We have a number of examples where a requested field has been created as a text field for example, but now we would like to change it to a user picker one and having that additional metadata next to the field is very helpful. Also we haven't received any complaints about broken filters, so I assume that change is applied everywhere.
Besties,
Velio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.