Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

A JIRA group is a convenient way to manage a collection of users. Users can belong to many groups. Groups are used throughout JIRA; for example, they can:

* Project roles are somewhat similar to groups, the main difference being that group membership is global whereas project role membership is project-specific.

On this page:

JIRA's default groups

When you install JIRA, three groups are automatically created:

Group

Description

jira-administrators

Typically contains people who are JIRA system administrators. By default, this group:

jira-developers

Typically contains people who perform work on issues. By default, this group:

  • is a member of the 'Developers' project role.
  • has the 'Browse Users', 'Create Shared Filter' and 'Manage Group Filter Subscriptions' global permissions.

jira-users

Typically contains every JIRA user in your system. By default, this group:

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

(info) 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.

Viewing groups

To see what groups exist, and where they are used:

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Choose > User Management. Select Groups to open the Groups page.
    (tick) Keyboard shortcut: g + g + start typing groups
  3. To see which permission schemes, email notification schemes, issue security levels and saved filters are using this group, click the group name.

Screenshot: the Group Browser

(info) 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.

Deleting a group

Before deleting a group it is recommended that you check whether the group is being used by any permission schemes, email notification schemes, issue security levels or saved filters. See 'Viewing groups' (above).

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.

(info) 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.

    See Managing Multiple Directories.


  • 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.

 

 

15 Comments

  1. Anonymous

    if someone belongs to  one group ,and the one could not view the issues of other group?

  2. Anonymous

    How do I change a group name?  I cannot find how to do this.

    1. Anonymous

      Renaming a group is not currently supported.

      See https://jira.atlassian.com/browse/JRA-1391

  3. Can we create sub admin who has access to a specific group and manage and edit users of that group only, if so how to set up this?

  4. 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...

  5. 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!

  6. One major problem in JIRA is that currently there is no way of knowing in which projects roles a groups is used, nor to document a group purpose (description).

  7. Anonymous

    Is it not possible to create groups which only have the ability to view/access certain projects?

    1. Anonymous

      This is done at the project level not the group level

      First define your group and your project

      Then remove al-users access from the project and add your new group with the desired permissions

  8. How can I configure a “read only” group to contain everybody — without haven ot add everybody seperaty?


     

     

     

  9. Can i have a screen where issue reporter can select multiple groups to have visibility on a issue. then notification is sent to members of these selected groups on ISSUE CREATE EVENT

  10. 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?

  11. Is it possible to print out a lists of users in the groups? 

  12. We have around 500+ Scrum Boards that show up when I click on "Manage Boards" link of Agile Drop Down. Is there anyway to categorize these boards so that I can only see the 50 that are relevant to me?