Problem Definition

JIRA is yet to properly support aggregated group membership as currently obtained in Crowd Server and Confluence.

• JIRA requires that external groups that an external user belongs to are from the same directory as the user for this membership to be effective.
• Using the REST endpoint {{curl -H 'Content-type: application/json' -X PUT -d ' {"membershipAggregationEnabled":true}

  ' -u <username> <base-url>/rest/crowd/latest/application}} which works in Confluence to turn on Aggregated group membership doesn't work in JIRA.

Suggested Solution

Support Aggregated group membership in JIRA Just like available in Confluence since Confluence 5.7.

Why this is important

This has an even higher value in JIRA since you can configure JIRA as your user server. Also migrating to Active Directory would become a lot easier.

Workaround

• You may need to ensure relevant groups are in the same directory as the affected JIRA user.