Is it possible to hide fields (custom & system fields) for search purposes. Like, if the user started typing "project = ACME", then the fields that are not available for this project won't be suggested at all?
At the moment with all our 10 projects and dozens of custom fields, it came to be impossible to use the search, either it is the simple one or the JQL.
Anyone knows how to achieve that in JIRA v5.1?
The thing is that 80% of my projects are prety slim, but those 20% have a huge number of custom fields. Putting "none" in their configuration will make these projects un-searchable. I don't want to cancel the ability of these projects' users to search their projects, create filters & gadgets. and so on.
I don't think there's a way to do this - the whole point of JQL is that it's powerful and can search anything. The project clause could be used anywhere in the search, and doesn't even have to be used at all.
I suspect you'd need to pull the whole of JQL apart and rewrite it to make this work.
I'd train your users to use the simple search instead, and think about how you limit your custom field contexts. Simple search DOES do the "is field valid for this project/issue type" limiting automatically, so I think your only option is to use that.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs