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?
Maybe these settings are different between dev and production?
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.
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?
Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...
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