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

Moshe Hajaj November 24, 2012

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
Answer accepted
Zul NS _Atlassian_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 24, 2012

Hi,

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

Moshe Hajaj November 24, 2012

Thank you Zul.

Does v5.2.1 has a release date already?

Suggest an answer

Log in or Sign up to answer