You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Greetings everyone,
I recently found when using advanced search in Jira Cloud, JQL criteria always added field type information after custom field's name automaticaly. Is there any way to hide this information to avoid confuse users?
Best regards,
Hi @InspectorD,
Personally I found this to be very helpful as we have many field names that are very similar in name and this helped ensure I was selecting the right field in my JQL search. I can understand how not everyone would feel the same way.
I'm not aware of any configuration setting that would allow this to be turned off. You might want to raise this as a suggestion to Atlassian here: https://jira.atlassian.com/browse/
-Jimmy
Thanks for your answer. Indeed, it's friendly when searching and identifying fields with similar names but have different field type in JQL search. (personally)
However, not everyone can adapt to search a custom field that having field type information, especially for users who migrating from server/data center version to cloud.
I will try to raise suggestion to Atlassian.
Have a nice day,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I find it useful sometimes, but I don't like how it has been done, and I know it makes it harder to read a query.
My design would have been to have some highlight that can show it, not insert text in yet more bracket-type things in the same font and colour, maybe an informational line below the search instead? I'm not a UX person, I can see that I don't like the current design, not sure how to do it better though.
Let us know if you raise a suggestion, I'll vote for it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The request has been submitted (hopefully I didn't write it wrong), hope to gather enough comments and suggestions as it's really a huge project from server migrate to cloud, any improvements that help reduce the workload and better user experience would be very useful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.