Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,619
Community Members
 
Community Events
176
Community Groups

Search with "assignee in (xxx)" is automatically converted to expert mode

Hello,

 

I search for issues with the basic search assigned to one person like this:Basic.PNG

This will give me the url: xxx/issues/?jql=assignee in (DHeinke)

When I open that URL again, it switches to advanced JQL mode and does not let me switch back:Advanced.PNG

 

I use the latest 8.3.0.

 

I also looked up the network traffic and found this:

URL: xxx/secure/QueryComponent!Jql.jspa

POST-DATA:

jql=assignee in (DHeinke)
decorator=none

RESPONSE:

{"errorMessages":["jqlTooComplex"],"errors":{}}

 

Any ideas how to fix this or is this a known bug?

1 answer

1 accepted

0 votes
Answer accepted

Hello Dirk,

Per your description, I believe you are being impacted by the following bug:

Can't switch to JQL Basic mode when username is uppercase

This bug causes the Basic search to be turned off when you search for any users with upper case letters in their username, not allowing you to switch back to the Basic mode.

Feel free to vote and watch the bug to receive notifications about any updates.

For now, the workaround available would be to type the user in lower case letters when searching for them using the Advanced mode, so you can switch back to Basic:

assignee in (dheinke)

Since username searches are case-insensitive, you should get equivalent results.

Let me know if this information helps.

Hello Petter.

 

The workaround seems to work, but it's hard to explain to the users, that you can create a search with Basic but can't modify it.

Anyways, thanks for your response.

 

Kind regards

Dirk

You are welcome, Dirk.

Indeed, this is a weird bug. We hope that it gets fixed in the next releases of JIRA.

Please, share your thoughts on the bug where our development team will be registering their progress.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events