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

0 vote

Hi,

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 Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

280 views 4 9
Read article

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