Best practice in Jira cloud for what groups where used in On prem server

[Michael Adams]

From a teammate.  A follow up question for Atlassian about Groups – this is the one where we talked about setting up very product specific groups that do not control overall access.

In the Server version we have a group in Jira called “PAM Management”:

It is a Jira specific group that is used to control who can see certain non-public dashboards/filters in Jira:

Some of these filter are public, but the “ALL PPAM Projects..” one is shared only with this group.

Question: In the cloud, would we continue to use groups to manage this use case?

If so, would such product specific groups that just control filters need to be set up and managed at the Org level by the Org admin and if we integrate with Okta, would these have to be set up in Okta? Both of which seem an overkill!

If not, what is the best practice?

I can provide screen shoots to show this if needed.

[__ Jimi Wikman]

Yes, you can still use groups to determine who can view filters.

You need site admin access to manage groups, which is one of the reasons many discourage the use of groups, as they often become black holes. Any project and user can use the groups to set permissions, but they have no idea who is in the groups. The site admins can see who is in the groups, but have no idea what they access.

How you manage this depends on how well your on- and offboarding processes work in terms of access and Jira cleanup, but also how many users you have in those filters and why they need to be restricted.

You might be able to use project roles instead in some cases if the filters are project based. This is a good way to delegate the user access responsibility down to the Jira Project Admins.

If you can explain in more detail what you need to accomplish, we will try to help you find a solution :)