Can fuzzy searching for the Issue Key / name be improved?

[Tim Brugman]

Example: http://toscani.nl/temp/logwork.jpg

When logging work on a large project it's getting really hard for us to get the correct Issue Key showing up.

In this example you can see that FCN-94 is easily the closest match for this search query, but it's not showing up. I've had to resort to searching for FCN-7, then FCN-8, then FCN-9, just so I get 10 unique results at a time. It slows down the logging process by a lot. Hope you can help.

[Volodymyr Krupach · Accepted solution]

Hi Tim,

Unfortunately it's not easy to improve. The searching is provided by standard JIRA API and it "works as it works".

Maybe other way: When "Issue Key" gets focus show the suggestion dropdown filled with few recently used issues. Would that work for you?

[Tim Brugman]

Hi Volodymyr,

I was afraid that might be the case. I'll present the problem to Atlassian.

Showing the last used issues should definitely be a time saver regardless!

[Volodymyr Krupach]

Hi @Tim Brugman,

Work Time Calendar version 2.7.0 for JIRA Server and  1.2.6-AC for JIRA Cloud include:

• To speed-up issue selection autosuggestion shows recent issues if nothing was typed