Quick search does not work for projects containing underscore

Hi

I am on jira 5.0

I observed that when you enter the issue key say JCC-2 in the quick search box and press enter you are directed to the issue.

This feature works fine for projects with project keys containing all alphabets. But moment i use this feature for projects containing underscore or numbers in the project key, it to bring up the issue.

Is there a workaround to this problem.

e.g.

JAA-2 works

HOTBALL-5 works

but

JOE1-55 does not work

COLD_BALL-45 does not work.

HAs anyone experienced this issue?

When i say does not work, it means that JQL window simply searches for summary ~JOE1-55 OR

description ~ JOE1-55 OR comment ~ JOE1-55 and returns the results for it; but not the issue JOE1-55.

Rahul

1 answer

1 accepted

This widget could not be displayed.

It's a known issue and (was) a contentious one. Atlassian did not officially support anything other than Alphabetic characters in the project keys. This has been causing problems for many years because that's far too limited. What's particularly frustrating is that many sites found and used the "enable other characters" flag, as you have, while Atlassian were gradually removing any vestige of code that could support us in the future.

From memory, the searching in version 5.0 only works fully and properly on projects that use letters and nothing else in the key. They announced that the flag for customised keys would be removed completely in 6.0, but have realised that is completely unnacceptable and from 6.1 will support letters, numbers and an underscore, and it will be complete support.

So, I'm afraid, you're a bit stuck for now, but if you went to 6.1, it should work fine.

Thanks Nic for your response. The JQL query issuekey=JOE1-55 works perfectly fine, its just the quick search which is messed up. But anyways, thanks for your response.

Do you recommend updating the project key in the database to get round this problem?

Rahul

If you can't wait until upgrade to 6.1, then it might be the only route. You could also create a new project with a searchable key and move your issues into it.

Personally, I'd prefer to simply warn the users that quick-search has a bug and it's fixed in 6.1, then wiffle about an upgrade :-)

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 06, 2018 in Jira Service Desk

A is for Activate: Share your top Jira Service Desk onboarding tips for new users!

Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :).  In the spirit of this month's  august-challenge, we're sourcing stories of Jira Service Desk activation fro...

593 views 25 15
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