nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can fixVersion autocomplete in JQL be made slightly smarter?

Mike Curwen NL

So I was typing project="myProjectName" and fixVersion="

and at that point, I see all versions, from all projects. I wonder if anyone knows if the fixVersion auto-complete suggestions can be trimmed to only include those from the specified projects, if the project JQL field is present?

This seems like a rather obvious enhancement, but unless the thing coming up with that list is presented with the entire JQL statement, I imagine it would be impossible to implement.

Accepted answers

Mike Curwen NL

I will answer my own question, by saying "not currently", and pointing everyone to the issue to vote for it.

https://jira.atlassian.com/browse/JRA-28239

All comments

Joe Clark

Agree this would be awesome, but it probably hasn't been done yet for exactly the reason you describe :-)

JamieA

Amen to that... a list of thousands, with 50 "Apr 2012 Sprint"s is useless. I don't see why the function could not take into account the clauses already entered... not trivial but not beyond the wit of Atlassian's superstar programmers.

JamieA

And the bigger the instance the more useless this is. Along with showing every possible custom field whether they're associated with the project or not. Delivering this could be considered a downpayment on the enterprise licensing!

unknown

Well, maybe parsing not completed JQL statement is not feasible, but maybe starting with @PKEY could make hint to provide only context values, so at the end I would write "@PKEY.Apr 2012 Sprint". There is just little step to provide that PKEY also (as result of on-demand parsing of already written JQL).

JamieA

Well, mostly you go into the issue navigator from a project context, so the selectedProjectId is already available. In which case all the options could be narrowed down to that project. Anyway, there's nothing developers hate worse than being told HOW to fix a problem. They should just know the problem is there, and magnified for their "enterprise" customers, and get on and JFDI!

Mike Curwen NL

I've 'poked Atlassian', apologies to them if that's not what that link is for. Is it just moderation, or is it to turn a question into something else (like, a feature request on JAC?)

Mike Curwen NL

ok, I've added this: https://jira.atlassian.com/browse/JRA-28239

Ruchi Tandon

I agree and understand the requirement in this case. Thanks for opening the improvement request. Thats is the best thing to do in this case. This way the developers can track the requirement and schedule it for appropriate sprints. I would also strongly suggest to vote on the issue, to increase its importance. For more information on how Atlassian implements new features and improvements, please refer this guide :http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy.

In the meantime, using the simple search is the only workaround that I can think of.

Mike Curwen NL

I will answer my own question, by saying "not currently", and pointing everyone to the issue to vote for it.

https://jira.atlassian.com/browse/JRA-28239

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jql

auto-complete