We want one set of users to access the function "Filters --> Advanced Issue Search" and one set of users to NOT access it. How can we set the permissions for this scenario?
Thanks in advance...
Hi @Ashraf B,
There is no control over access to that menu option. There are a couple of things that indirectly impact what users can/can't see, however:
Hope this helps!
Thanks @Walter Buggenhout _ACA IT_
But, if we go by "...they will only see the issues in projects where they have browse project permission..." So, the users whom I assign the tickets, will neither see the Project, nor the tickets assigned to them under that.
Is that correct?
Hi @Ashraf B ,
Browse project is a permission that you set for every single project in your Jira instance.
If you have multiple projects in Jira, then you manage access for each project separately. But again: if your project permissions are well defined, people will only be able to view the issues from the projects they have been granted access to.
It is best practice to set project permissions by project roles first, and then by assigning groups to these project roles. You should only create groups for people who need project access. It doesn't make much sense to create groups for people who don't need access, as you won't be using that group anyway.
I would like to recommend you to read about project permissions in this support article to get a deeper understanding.
Thanks @Walter Buggenhout _ACA IT_
But, if we go by "...they will only see the issues in projects where they have browse project permission..." So, the users whom I assign the tickets, will neither see the Project, nor the tickets assigned to them under that. 'Cause this access grant / denial is required for licensed users who will work on the tickets assigned to them, but they should not access or fetch or download tickets assigned to other users.
@Ashraf B hi,
I'll pitch in by saying first of all that @Walter Buggenhout _ACA IT_ states correctly how Jira works with projects permissions. The latter I strongly believe that is a topic in which you should invest in reading. After reading that I would suggest for you to invest some time reading about issue-level security, which will come in handy, especially about the last sentence of yours "but they should not access or fetch or download tickets assigned to other users.".
Hope all the above helps.
Thanks @Alex Koxaras, I've set the Issue Level Security and the users can see and work on only the issues that have been "assigned" to them.
But, I have observed users can View & Export ALL DATA (their assigned issues as well as issues assigned to other users) through Filter --> Advanced Issue Search.
I will re-check if that is the case and if yes, I'm trying to plug that...
Users will be able to see and export all issues to which they have visibility:
If a user can see something he/she shouldn't then you should revisit your plan. Permissions and issue-level security works flawless (so far).
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
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