Jira advanced search autocomplete eats next word

[stdedos]

If I have a complete query, and I try to add more things in the middle of it, words get eaten up:

e.g.:

filter = "x" and assignee = currentUser() ORDER BY updated DESC
#                              caret here ^

filter = "x" and assignee = currentUser() anORDER BY updated DESC
#                                caret here ^, press "Enter" to autocomplete 'AND'

filter = "x" and assignee = currentUser() AND  BY updated DESC 
#                                  caret here ^ 

filter = "x" and assignee = currentUser() AND tes BY updated DESC 
#                                     caret here ^  

I know the workarounds, but I don't think it's hard to fix it! 

[Mirek · Accepted solution]

Hi @stdedos ,

The issue that you are facing is in group of one of the most annoying usability bugs that exist in auto-complete JQL advanced search.. I was not able to find exactly your problem but very similar problems (or even worse) are described here..

https://jira.atlassian.com/browse/JRASERVER-65022

https://jira.atlassian.com/browse/JRASERVER-68452

Overall at least for your problem the workarounds exist - for example put the cursor one whitespace before the next argument ..

filter = "x" and assignee = currentUser() a ORDER BY updated DESC
#                              caret here ^

and I agree with you - this should be fixed however I think we cannot do more than just report this and vote for the tickets that are created.

[stdedos]

I guess the most annoying thing is that "JQL advanced search" is a very powerful, and versatile feature, and sometimes it is so crucial to "play" with it so much.

That makes any kind of UX lag / bug to be disproportionately annoying!

Maybe if they just "dump JQL down", then we wouldn't complain as much 😂😂😂😂😂

[stdedos]

bq. The issue that you are facing is in group of one of the most annoying usability bugs that exist in auto-complete JQL advanced search. [...] and I agree with you - this should be fixed however I think we cannot do more than just report this and vote for the tickets that are created.

Oh, I see ... They are Priority: Low.

Apparently, you think that this is okay ...