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 votes
Accepted answer

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
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,088 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