nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to control who has access to Filters and Advanced Issue Search in JIRA SM Cloud?

Ashraf B

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?
Please suggest.
Thanks in advance...

Accepted answers

Walter Buggenhout

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:

The filters > search functionality is only available to users with a Jira license. JSM Customers - who can only access tickets through the customer portal - won't have access to this functionality (and essentially to all internal Jira functionality).
While people may have access to the search functionality itself, they will only see the issues in projects where they have browse project permission. So rather than trying to disable the search functionality, you could/should review project permissions in your Jira instance.

Hope this helps!

All comments

Walter Buggenhout

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:

The filters > search functionality is only available to users with a Jira license. JSM Customers - who can only access tickets through the customer portal - won't have access to this functionality (and essentially to all internal Jira functionality).
While people may have access to the search functionality itself, they will only see the issues in projects where they have browse project permission. So rather than trying to disable the search functionality, you could/should review project permissions in your Jira instance.

Hope this helps!

Ashraf B

Thanks @Walter Buggenhout

Walter Buggenhout

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.

Ashraf B

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.
Please suggest...

Regards,
Ashraf

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management