You can create and delete groups according to your organisation's requirements.

Please Note: If you are using External User Management, you will not be able to create, delete or edit groups or group membership from within JIRA; and 'Automatic Group Membership' (see below) will not apply. However, you can still assign groups to project roles.

Please Note: The 'Filter Group' form restricts the list of groups shown to those that match the 'Name Contains', with a specified maximum per page. Click the Filter button to refresh the list with the restricting filter.

Adding a group

To create a group, enter the new group Name in the Add Group form in the Group Browser and click the Add Group button.

To delete a group, click the Delete link for that group in the Group Browser. The confirmation screen that follows explains that users will be removed from the group through its deletion.

Be aware of the impact this may have on users in that group. For example, if that group membership was the sole conveyor of a permission for a user, then the user will no longer have that permission.

Editing group membership

To edit a group's membership, click the Edit Members link in the row for that group in the Group Browser. This takes you to a form allowing you to add users to or remove them from the group.

Please Note:

If the group has the 'JIRA System Administrators' global permission, you cannot edit its membership unless you have the 'JIRA System Administrators' global permission.

If you have a user limited license (e.g. personal license) and have reached your user limit, you will not be able to assign any further users to groups with login permissions (i.e. jira-users permission) without first reducing the number of users with login permissions.

Automatic group membership

To automatically add newly-created users to a particular group, you can either:

Notes

Multiple user directories:You may define multiple user directories in JIRA, so that JIRA looks in more than one place for its users and groups. For example, you may use the default JIRA internal directory and also connect to an LDAP directory server. In such cases, you can define the directory order to determine where JIRA looks first when processing users and groups.
Here is a summary of how the directory order affects the processing:

The order of the directories is the order in which they will be searched for users and groups.

Changes to users and groups will be made only in the first directory where the application has permission to make changes.

Nested groups:Some directory servers allow you to define a group as a member of another group. Groups in such a structure are called 'nested groups'. If you are using groups to manage permissions, you can create nested groups to allow inheritance of permissions from one group to its sub-groups. See Managing Nested Groups.

Anonymous

Is is possible to have "Parent Groups" so that user management is minimized and easily changeable? For example, I have 4 role groups that determine what actions specific users can take (across multiple projects) but 3 category groups that help to determine who would work with issues(tasks) within that category.

The categories might be Dog, Cat, and Mouse, and the roles might be groomer, owner, walker, exterminator.

Dog > owner, groomer, walker

Cat > owner, groomer

Mouse > owner, exterminator

Not the best example but you get the idea. The walkers might have to help out with cat issues one week so they all need to be able to see those items. With 500 walkers manually adding them to another group would be very time consuming...

Anonymous

I have a read-only LDAP with local groups setup, and want to give certain groups permission to login.When I do this, every new user gets added to those groups.I understand this is exactly as is described above, but I don't understand why that is the only configuration. It makes no sense for a user of LDAPgroup1 to be added to LDAPgroup2 simply because both groups can login.If I wanted new users to join a group automatically, I would have configured it that way!

In a project: how can I grant permission to one group or project role to create issues of any issue type and then grant permission to another group or project role to create issues of only 2 of the issue types?

If I create a new user with developer profile, I have to add him to the jira-users and jira-developers group in my active directory. What do I have to do to have to put him only in the jira-developers group? I've read somewhere that putting one group inside other can create performance problems.

We will be using multiple customers via one Service Desk . hence we will have many SD Customer access log ins. Now in order for them to be able to see each other issues via customer portal - shall I create GROUP with each company name and add same company's user names in it ?