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; } } }

Unable to assign default to certain groups

Joshua Stokes

Hello,

We have several Groups that were created that were not 'out of box' groups (Under products > Jira Service Management) these groups we have created are synced and managed from an external directory.

When I try and make one of these external groups a default I get an error message -

Even after a few mins or days it is still the same.

Does this have something to do with these groups been created externally?

Like wise the out of box 'stakeholders' group has no members assigned, but I am unable to remove this as default as well.

I have admin permissions to Jira as well.

Any advice on this one? Or is it because these groups and managed externally, we cannot make them a default?

Accepted answers

Piyush Annadate _ACE Pune_

Hello @Joshua Stokes ,
Welcome to the Community !
Any groups (& users) sync'd from external directory, can be MANAGED BY EXTERNAL DIRECTORY ONLY.
You cannot make changes to it. If you want those to be managed locally, you are required to disconnect that from external directory else you may contact Atlassian to disconnect the group.

Now, the actual issue, if you see the error, then the group cache seems to have an issue.
Can you check from browser console (f12 or developer option and check the console) for any error and share?

[Edit: Actual answer - https://community.atlassian.com/forums/Jira-Service-Management/Re-Re-Unable-to-assign-default-to-certain-groups/qaq-p/3015053/comment-id/206145#M206145]

All comments

Piyush Annadate _ACE Pune_

Joshua Stokes

Hello,

Thanks for the quick reply, when I select the 3 dots on a product group, and select 'Update default group setting' it does show some errors in the console -

The groups I am trying to make default are externally managed groups...

Can I assume that we CANNOT make externally managed groups defaults?

Cheers.

Joshua Stokes

Hey @Piyush Annadate _ACE Pune_

Any luck with the error message, or pretty generic?

Thanks for your help with this one, keen to provide some answers to my seniors ASAP :-)

Cheers.

Piyush Annadate _ACE Pune_

Hi @Joshua Stokes ,
Something slipped from my mind, actually you cannot assignee a READ ONLY group to default group.

Since, the default group mechanism add a new users into default group by Atlassian, and that should be local wherein Atlassian can managed; with external they cannot.

Piyush Annadate _ACE Pune_

Answer is above https://community.atlassian.com/forums/Jira-Service-Management/Re-Re-Unable-to-assign-default-to-certain-groups/qaq-p/3015053/comment-id/206145#M206145

Joshua Stokes

Thanks @Piyush Annadate _ACE Pune_

Are you able to explain that last paragraph a bit better sorry?

Thanks for your help.

Jonas Nilsson _ Unitlane

One practical rule that helps here is: use internally managed groups for default app access, and use SCIM-synced groups for identity-driven membership and permission mapping.

Default groups need to be writable by Atlassian, so even a technically correct external group is still the wrong anchor for automatic placement. It also keeps billing easier to reason about later, because you can tell whether the seat exists because of default access, synced access, or both.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

default

jira-service-management-cloud

jira-service-management