In jira v5.2, when switching from basic search to JQL, the custom field looses its name

I'm testing the new JIRA v5.2, and especially its new Issue Navigator improvements.

Well, it looks good, and the improvements are definitely expected. Except for this minor "bug":

If I start to compose my filter in basic mode, adding some custom fields, and then switching to JQL (advanced), some of the custom fields are not displayed using their names, but rather are written like this - cf[10027.

Anyone, had this problem before? Is it something that is fixable?

1 answer

1 accepted


You are facing this bug which will be fixed in JIRA 5.2.1

Thank you Zul.

Does v5.2.1 has a release date already?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,233 views 14 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot