Here's my situation. We have a LDAP directory which contains users and their group memberships. However, not all groups are useful in JIRA. Some are used for other applications.
I'll give an example:
"user1" is member of "jira.group1", "jira.group2" and "notjira.group1"
Currently, when user1 logs in, all 3 groups are created in JIRA.
I'd like to make only groups in "jira." format be created automatically on login.
I've looked at this doc as suggested in other Answers posts, but that's not quite what I need. I want any user on that LDAP to be able to connect to JIRA regardless of the groups they belong to, I just don't want useless groups to be created when users belong to groups used in other apps.
Thanks for any help!
If you change your Group Object Filter as mentioned by the Example 2 of that same doc and add the specific group names you want JIRA to retrieve, you should be able to get only the groups you want.
Please note the Group object filter field has a 255 character limitation in the database, so you won't be able to list too many groups in the field.
If you need more groups than you are able to filter, you may want to put them all as a nested group of another "parent" group and filter by this parent group with something like the query below
or put them on a separate DN and only get groups from inside that DN using the "Additional Group DN" field.
This doc may also be helpful here.
Hope this helps
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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