New Jira (local) groups end up read-only

On our production JIRA server (5.2), when I create a new group in Jira, it ends up being read-only by default and does not propagate itself into Crowd. This does not happen on our dev server, where the group is automatically write-enabled and pops up into Crowd immediatly. Where is that behavior set?

2 answers

I checked the said permissions and they're the same on both sides. Actually, I see 8 permission checkboxes in Crowd 2.6.0 instead of the 2 documented here, and no Read-only option.

Hi Luc, The settings are available in JIRA, where you configure the Crowd directory. Regards, Geert

Modifying the Crowd directory in Jira requires a "local user" (i.e. defined in the JIRA Internal Directory as opposed to Crowd) but while creating such a user works, its login always fails. Can Jira's login work without Crowd?

It cannot if you enabled SSO. One option is to create a new directory with the same settings, move that one "up" and then disable/remove the old one.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,405 views 15 19
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you