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,556,679
Community Members
 
Community Events
184
Community Groups

Limiting the options in a field in the filter screen

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.

1 answer

1 accepted

0 votes
Answer accepted
Radek Dostál
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 21, 2023

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events