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.
Is there a way to reduce the number of options in a field in a filter. We have clients with access to 1 project but when they use the filter, if they leave the Projects filter set to All, they see ALL possible option values in all available fields. This is a serious data security issue in 2 ways:
1. ALL people fields will show ALL users (plus part of their email address), including other client users that do not belong to their project;
2. ALL custom fields will show ALL possible values, including a Client Name field we have - this allows every client of ours to see the full list of all other clients that we are working with.
Thanks.
That's how it's built, and it cannot be changed. This is something for Atlassian to address and I think there are some requests for this on https://jira.atlassian.com/issues/?jql= but might be tough to filter it out with a good query.
The way the JQL query is implemented doesn't really leave much of a room for this right - because you write the whole thing, in any order you want. It would need to be completely changed to facilitate such a thing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.