The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

JQL on custom field of type "Select List"

Kristin Palmer
Contributor
February 16, 2021

Historically I have been able to run JQLs on custom fields with type "Select List (single choice)" in the following way:

  • "My Custom Field Name" = "A valid entry"

But I am now receiving errors and need to include a [dropdown] suffix. This syntax is working without errors: 

  • "My Custom Field Name[dropdown]" = "A valid entry"

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? 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Velizar Borisov
Community Champion
February 23, 2021

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

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events