Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restricting who can create filters. Edited

We are trying to prevent people in our support project from seeing issues we do not want them to see. We have in place currently Issue Security so the users can only see Issues that they created (Reporter) or is assigned to them unless they have a specific role (Admin) or in a group we created (Supervisor). This works to a degree but now we have a user that is responsible for all issue from certain accounts but they don't want them to see everything. My suggestion to the owners is to create a new issue security level that we can set for the issues for those accounts and put this user in a role associated with this security level. We would also have the reporter, assignee, admin and Supervisor. This works in theory but the owners (who are also the only ones that can assign an issue) do not want to do this manually. In Automation I am able to capture the name of the security level in a user created field based upon the account entered during issue creation and once again that works fine. I cannot get that value loaded into the Security level for the issue. My Supervisor (read owner) is getting impatient and wants to remove issue security and restrict who can create/edit filters. She basically wants just the Admin and supervisors to be able to create and distribute the filters we want the users to have. Personally I would prefer to find a way to conditionally set the security level automatically. BTW our budget for Jira is already exceeding what was set so no plug ins and we are using Jira cloud. Sorry for the rambling question

1 answer

0 votes

There's no control over who can create a filter - searching really is the core thing people need from an issue tracker, and being able to save and re-use filters is a massive benefit.  I'd forget about trying to restrict that, you'll just annoy people and make them less productive.

However, sharing filters can (and often should) be controlled.   It's done by the global permission "Create Shared Objects".  Only the groups with that permission can share them.

Without Apps, that's the only thing you can do about sharing of filters.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Jira issue check and more advanced commit verifications for Bitbucket DC

Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....

31 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you