Documentation for JIRA 6.3. Not using this? See below:
(JIRA 6.2.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

On this page:

Viewing users

To view a list of JIRA users:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > User Management.
    (tick) Keyboard shortcut: g + g + start typing users

  3. To restrict the list of users shown, use the Filter form at the top of the page.
  4. To view details and login information about a user in the list, click their Username or Email Address.

Adding users

Users can be created via any of the following methods:

  • Add the user directly into JIRA — see Creating a user below. You can create one user at a time, using this method.
  • Invite users via email — see Inviting Users below. You can invite multiple users at the same time, using this method.
  • Allow users to sign up — see Enabling Public Signup.
  • Automatically create users when issue/comment creation emails are received from unknown email addresses — You can use a mail handler to allow JIRA to create issues or comments via emails received. The handler can also be configured to create new users based on the sender's email address. See Creating Issues and Comments from Email.
  • Connect to an Internal Directory with LDAP Authentication — see Copying Users on First Login.

(info) Please Note: If you have a user limited license (e.g. starter license) and have reached your user limit, any further users created will not have permission to log in to JIRA

Who can see a user?

Any JIRA user can see another JIRA user's full name and username, for example, see Mark Lassau. The email address visibility is controlled by a configuration item; see "User email visibility" on the Configuring JIRA Options documentation page.

Group membership and the ability to edit users is only available to administrators.

Any JIRA user can see their own details, including group memberships, update their own password, and change certain user preferences (for example, time zone and language).

Creating a user

To create a user:

  1. Open the User browser (see Viewing Users above) and click the Create User button to open the 'Create New User' dialog box.
  2. Enter the Username, Password, Full Name and Email address.
  3. Optionally, select the Send Notification Email  check box to send the user an email containing:
    • their login name; and
    • a link from which to set their password (this link is valid for 24 hours).
  4. Click the Create button.

Inviting users

You can invite one or more users to JIRA via email. Note, JIRA's SMTP mail server must be configured to send notifications before you can invite users via email.

To invite users to JIRA:

  1. Open the User browser (see Viewing Users above) and click the Invite Users button to open the 'Invite Users' dialog box.
  2. Enter the email addresses of the users that you want to invite. Enter each address on a new line or separate addresses using commas.
    Note, you cannot invite users by sending an invitation to a mailing list.
  3. Click the Send button to send the invitations.
    • Each invitation can only be used to create a user under the email address that it was sent to, and can only be used once.
    • Each invitation will expire seven days after the day it was sent.
    • Your user license count will not be affected until users accept the invitation and the users are created. 
    • Users that are created via the invitation will be added to the 'jira-users' group.
     

Assigning a user to a group

When a user is created, they will be added to any groups that are set up to have new users automatically added to them.

To change a user's group membership:

  1. Locate the user in the User browser (see Viewing Users above) and click the Groups link in the Operations column.
    This will display two lists; the one on the left shows all Available Groups, and the one on the right shows the Current Groups to which the user currently belongs.
  2. Choose a group(s) and click the Join selected groups or Leave selected groups buttons to add/remove the user from the selected groups.

(info) Please Note: If you have a user limited license (e.g. starter 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.

Assigning a user to a project role

Assigning a user to a project role enables them to fulfil a particular function in a particular project.

To assign a user to a project role:

  1. To view a user's project role membership, locate the user in the User browser (see Viewing Users above) and click the Project Roles link in the Operations column. This will display a table showing all the projects and project roles that exist in JIRA, and the user's current project role membership for each project:

  2. Click the Edit Project Roles button. The check boxes will then be available for you to select (to add the user to a project role) or clear (to remove the user from a project role).

Changing a user's name or email address

To change a user's name or email address:

  1. Locate the user in the User browser (see Viewing Users above) and click their Edit link in the Operations column.
  2. In the resulting form, make the required changes the user's Full Name and/or Email address.
    (warning) Do not clear the Active check box unless you want to deactivate this user.
  3. Click Update to confirm the change.

Changing a user's password

To change a user's password:

  1. Locate the user in the User browser (see Viewing Users above) and click their Username. This displays the user's details, below which are several links.
  2. Choose Actions > Set Password.
  3. Enter and confirm the new password.
  4. Click the Update button.

Changing a username

(info) This feature is only available for downloadable instances of JIRA. It is not available in JIRA On Demand.

JIRA Administrators can edit any Username in the JIRA Internal Directory (this is often referred to as the "rename user" feature). This ability is important to have if you wish to connect JIRA to an LDAP directory that does not follow the same username conventions. You also may want to do this if a staff member wishes to change their surname. Once the Username is changed in the internal directory, all parts of the JIRA interface display the updated Username.

Note: The Username is for the JIRA Internal Directory, and should not be confused with the user's display name, or Full Name, in the JIRA system.

There are some important exceptions that will prevent you from using this feature, of which you should be aware:

  • Only JIRA Administrators can perform this function.
  • JIRA cannot update external users – for example, users that are coming from an LDAP server or Crowd instance – it can only update users stored in the JIRA Internal Directory. (However, JIRA can update JIRA users stored in an "Internal Directory with LDAP Authentication.")
  • If you are using your JIRA instance as a JIRA User Server for other applications, e.g., Confluence, you will not be able to use this feature. If you aren't sure about this, check under User Management > JIRA User Server to confirm that no external applications have been configured to use JIRA as a Crowd Server.

Using a JIRA User Server for other applications

Icon

When JIRA is being used as a User Server for other applications, e.g. Confluence, we don't allow a user rename on the JIRA server as this would not be recognised on the other server. (And the other application would think that user was deleted and a new user was added.)

If you are happy to accept this behavior, then you can set a flag to allow the rename, as documented in the Knowledge Base article: Cannot rename users despite upgrading/installing JIRA 6

We are hoping to add the ability to detect renames from a remote Crowd or JIRA server sometime soon, see JRA-32200.

To change a username:

  1. Locate the user in the User browser (see Viewing Users above) and click their Username. This displays the user's details, below which are several links.
  2. Choose Actions > Edit Details.
  3. Edit the Username.
  4. Click the Update button.

Adding a property to a user

A 'Property' is an extra piece of information about a user that you can store in JIRA. A Property consists of a Key of your choice (eg. 'Phone number', 'Location') plus a corresponding Value (eg. '987 654 3210', 'Level Three'). Other than adding property data to the specified user, User Properties do not have an effect anywhere else in the project.  Plugins, however, can frequently use this data.

To create a new Property for a user:

  1. Locate the user in the User browser (see Viewing Users above) and click their Username. This displays the user's details in a box.
  2. Choose Actions > Edit Properties. The Edit User Properties screen will be displayed:
  3. Enter the new Key and its Value, then click the Add button.

Deactivating a user

JIRA administrators can 'deactivate' a JIRA user, which disables that user's access to JIRA. This avoids the need for a JIRA administrator to delete the user's account from the system.

This feature is useful when a JIRA user leaves an organisation because a deactivated user's history of JIRA activity is preserved on the system. If a user with a deactivated JIRA account rejoins the organisation at some point in the future, their JIRA user account can be re-activated.

To deactivate a user account:

  1. Locate the user in the User browser (see Viewing Users above) and click their Edit link in the Operations column.
  2. In the resulting form, clear the Active check box.
  3. Click Update to confirm the change.
    (info) To re-enable the user again, repeat the steps above but instead, select the Active check box.

While a JIRA user account has been deactivated, that user:

  • Will no longer be able to log in to JIRA.
  • Cannot be assigned issues or added as a watcher to issues (whenever issues are created or edited). However:
    • A user who was assigned, was watching or had reported any issues in JIRA before their account is deactivated, will still appear as the respective assignee, watcher or reporter of those issues. This situation remains until another user is specified as the assignee or reporter of these issues, or the deactivated user is removed as a watcher from them.
    • A user who voted on any issues in JIRA before their account is deactivated, will continue to appear as a voter on these issues.
  • Will continue to appear on the JIRA user interface with '(Inactive)' displayed after their name, where applicable.
  • Can still be used to filter issues in a JIRA search query.
  • Will not receive any email notifications from JIRA, even if they continue to remain the assignee, reporter, or watchers of issues.
  • Will not count towards your JIRA user license limit. Refer to the JIRA Users global permission explanation on Managing Global Permissions for more information.

(info) Please Note:

  • Users who are project or component leads cannot be deactivated. To deactivate these users, assign other users as the relevant project or component leads first.
  • Any JIRA site's users who are configured in an external Atlassian Crowd user directory and deactivated in Crowd, will be deactivated in JIRA.
  • With the exception of JIRA users configured with 'delegated LDAP authentication', JIRA does not deactivate users who are configured and deactivated/disabled in an external Microsoft Active Directory or LDAP-based user directory.

Deleting a user

Rather than deleting a user, we recommend that you deactivate their account instead (as described above). Deactivating a user's account will prevent that account from being used and prevent anyone from being able to log in to JIRA using that account. However, it will preserve that user's history of activity on JIRA.

To delete a user:

  1. Locate the user in the User browser (see Viewing Users above) and click the Delete link in the Operations column.
    The confirmation screen that follows will summarise any involvement of that user in the system by showing current issues assigned to and reported by that user, etc. These connections between the user and other parts of the system may prevent the deletion of that user. 
  2. Take any actions required to disassociate the user with JIRA. These may include:
    • Reassigning any issues assigned to the user.
    • Bulk-editing the issues created by the user and change the 'Reporter' to someone else. You'll need the 'Modify Reporter' permission to do this. You will also need to allow editing of closed issues if some of the issues the user created are closed and you do not wish to reopen them.
    • Changing the owner of shared dashboards owned by the user. See Managing Shared Dashboards.
    • Changing the project lead for any projects that the user is a lead of.
  3. If there are no issues assigned to, or reported by the user, and the user has not commented on any issues, the confirmation screen will display a Delete button. Click this to proceed with the deletion.

Please Note:

  • You cannot delete a user from JIRA if they have performed any of the following actions:
    • reported or been assigned to any issues
    • commented on any issues
  • The filters and dashboards of a user will be deleted when the user is deleted, regardless of whether the filters or dashboards are shared with other users.
  • Any numbers of issues which have been reported by or assigned to the user you are attempting to delete, are respectively hyperlinked to a list of the individual issues (in the Issue Navigator).

Notes

  • If you are using External User Management, you will not be able to create, edit or delete users from within JIRA; but you can still assign users to project roles, and create/edit/delete user properties.
  • If you have JIRA connected to either a delegated LDAP directory or an LDAP directory set to 'Read Only' (see Connecting to an LDAP Directory for details), you will not be able to change a user password from within JIRA.
  • 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.

 

 

46 Comments

  1. Anonymous

    Now i have a list more than 100 person to be added. If there is any method to import these users at once.

    1. Anonymous

      unfortunately not

      1. There are a few plugins that do this, I thought? Otherwise use the SOAP API addUser and your favorite scripting language.

    2. The csv import facility can create users, so that's one possibility you might be able to leverage:

      http://confluence.atlassian.com/display/JIRA/Importing+Data+From+CSV

  2. Hey, when you import issues from a spread sheet it asks if you want to create users....  so you can get the account created, but nothing set (e.g. passwds)

  3. Anonymous

    We are considering using JIRA at my company.  I need to know if it's possible to put restrictions on users so that they can create issues, but only view those issues that they have created and nothing else.  We will have several projects and would like clients to be able to log bugs, but not have visibility into the rest of our projects, etc.  

    Can anyone confirm that it's possible to segment the system and restrict permissions in this way?

    Thank you. 

  4. This page should document what are considered valid user ids. For instance, I thought earlier versions of JIRA (< 4.3) did not allow special characters for user ids (for example blanks) but apparently now this is possible. Please clarify what is allowed and when that changed. Thanks.

    1. Really? That's wacky! I'd like to see JIRA (and Confluence, Crowd etc) only accept what Active Directory considers valid userids. Too much pain otherwise later on trying to get everything working. Mind you, if the userids were easy to change it might not matter as much.

  5. Anonymous

    To deactivate a user, the instructions say:

    To deactivate a user account:

    1. Locate the user in the User Browser (see Viewing Users above) and click their Edit link in the Operations column.
    2. In the resulting form, clear the Active check box.
    3. Click Update to confirm the change.

    However, when you click on EDIT the form allows you to change the USER NAME and and USER"S EMAIL  There is NO ACTIVE check box on 

    this form.  I thought it might be a browser issue.  I tried it with IE and Chrome.

    1. Hi there,

      Are you using JIRA OnDemand? If so, then please be aware that the deactivate user feature is not available in this implementation of JIRA - this feature is only in the downloadable and installable 'behind the firewall' implementations of JIRA.

      We've added a note near the top right hand side of if the page, indicating that some of this page's functionality is not available in JIRA OnDemand.

      As an alternative, you can use Atlassian OnDemand's application access features to restrict a user's access to one or more applications in Atlassian OnDemand (i.e. JIRA OnDemand).

      (info) See also Restricted Functions in Atlassian OnDemand for more information about the differences in features between JIRA OnDemand and installable 'behind the firewall' implementations of JIRA.

      Hope this helps.

      Cheers,

      Giles.

      1. Anonymous

        Hi Giles,

        Really strange to me that you can't deactivate a user in on-demand.  Seems like a very useful feature.

        Can you help outline what configuration we want to setup so that 

        • user no longer counts against your active user license
        • user can't access the site
        • user doesn't get any type of notifications, etc.

        Thanks,

        Brian

        1. Hi Brian,

          User management works a bit differently in JIRA OnDemand. This document should help answer your questions:

          Managing users and groups for sites with multiple OnDemand applications

          Kind Regards,
          Andrew

  6. Is there a way to search for a list of all users in the JIRA Internal Directory?  We have two directories and I only want to see the users in 'JIRA Internal Directory'.  OR, can I sort the list of users by Directory?  OR, as a workaround, is there a way to export the entire user list to Excel?  

  7. Anonymous

    I have imported from an .csv and did somethong wrong. How can i BULK delete users ?

  8. Anonymous

    Looking for some quick advice!

    Currently only our systems team and developers use JIRA but we would like to be able to share Issue/development progress with the entire business (where appropriate) but in a read only fashion.

     

    The problem is the System team is 20+ people where as the company has over a 500 employees so we currenltyonly have 25 licences. Do we need 500 licences? or is there a way to share Issues in a read only manner with the business users? The share link on the issue appears to require a login otherwise it would be perfect

     

    Many thanks for your help in advance

    1. Anonymous

      You could create accounts for the other 500 plus employees and add them to a group you've created such as 'external-viewers' that has permission to view issues in each of your projects. Just make sure these users are not in the jira-users group, as those ones count towards the licence limit.

  9. Anonymous

    Hi,

    I am using JIRA standalone instance. I have an user limited license of 500 users and I have imported 423 user accounts from Active Directory. However, not all user accounts are valid. Some are dummy user accounts such as 'lan_admin', 'admin_1'. Only 300 user accounts are valid.

    So my question is this. Will JIRA allow me to include only 77 (i.e 500-423) more user accounts or to include 200 (500-300) more user accounts.

    There will not be any login from the dummy user accounts.

    1. If you remove a user from all JIRA groups it will not count towards your user limit

  10. It looks like the "Deactivating a user" steps are out of date (as are a lot of pages in this documentation). You go to "Application Access" to remove access to your Jira. Well thats how I found to do it.

  11. Anonymous

    I'm unable to Deactivate, but I can Delete. Also, ditto what Rob Boyett said, you can drop access to apps, but not just deactivate the account, which I would like to completely deactivate.

    1. Hi,

      It sounds like you and Rob are using JIRA OnDemand, which manages users differently. This documentation is intended for people who are using the downloadable version of JIRA.

      This documentation may be helpful: https://confluence.atlassian.com/display/AOD/Managing+application+access

      Kind Regards,
      Andrew

       

  12. Anonymous

    Is there any way to add two different emails to one user?

    Thanks a lot.

  13. Hey guys,

    Since JIRA 6 I don't see a possibility to manage project roles for a user on Edit Project Roles screen. I see only existing projects for this user but cannot add a new project(s) for this user to assign this user to a role for multiple projects as it was before.

    1. Hi Greg, I took at look at this and I don't see any way of adding a New Project in this screen either. You could log a JIRA issue on this, but for now I've updated the procedure for adding a Project Role to include adding users to the new project as well (as I think this is the only workflow for doing this at the moment).

  14. i have followed the same steps to create user in JIRA it was successfully done thanks for the documentation you people made it easy to learn

  15. We currently have 2000+ users that needs to be DEACTIVATED (Unticking the ACTIVE checkbox). It seems to be pretty tedious opening up each account and update it one by one, is there any other way to accomplish this?

    1. Not that I know of using REST or SOAP. May have to do a RESTful approach for it as I used in http://jiradev.blogspot.com/2011/08/adding-components-to-jira-automatically.html but it's not pretty 

      1. Thanks for the suggestion Matt. I haven't tried it yet but I was thinking/wishing/contemplating there would be an easier way.

        1. JIRA CLI and curl does the trick!

          It's kinda a bit tricky calling EditUser.jspa since it needs a second authentication.

  16. Please provide some information regarding who is able to see and edit the user properties. Is this information visible to the users, all of them? or just to jira-administrators.

    1. "Normal" users will always be able to see another user's full name and username. (eg see https://jira.atlassian.com/secure/ViewProfile.jspa?name=mlassau). Whether the email addresses are visible or not is controlled by a configuration item - see "User email visibility" on the Configuring JIRA Options documentation page.

      Further information (eg group membership) and the ability to edit is only available to administrators.

      A user can see their own details including group memberships, update their own password, and change certain user preferences (eg time zone and language).

  17. Anonymous

    hey there,

    i have a questions about deactivating an user.

    when i cklick ( as an admin) on the "edit" button in the operations column...no checkbox appears.
    the user i want to deactivate is not in an component or project lead.
    Can anybody help me?

    Thanks a lot

    BR
    Phil


  18. Anonymous

    Hi all,

     

    I have a question about changing a users email address.

    I need to change email-address of a goup of user, not only for one user.

    The reason is that the suffix of many users email addresses was changed because the company name changed.

    So it is not longer Max@companyA but it is Max@companyB and this for a lot of users.

    How can I do this?

    Thank you very much for your help!

     

    best regards

    Ariane

     

  19. Anonymous


    Is there anybody who has an idea to administrate the follwing:


    A subscribed filter as email, today provides a standard layout with the following information:  

    • key 
    • Summary


    It should be checked whether the following information can not be included in this ABO-mail:

    • Editor
    • status
    • due date

    Thanks

    Ariane

  20. I am not seeing the option to edit users, only groups and project roles. We are using users through ldap, does this have something to do with it? We are using JIRA Download.

    1. Hi Iris, I checked with our Support engineers and they said, "sounds like normal behaviour when using LDAP in Read-Only mode." If you want/need to make edits, it's best to do this in active directory/LDAP.

  21. Anonymous

    Would be nice (new feature) to search on those that have failed login attempts, or not logged in at all.

    This way, as the admin, I could contact these people to see if they are having issues, or if their account has been hacked. Right now, there is no easy way without looking through the whole user list for this information that is clearly there, just not sortable or seachable.

  22. I am currently testing/evaluating JIRA 5.2.11.  I've found the disable checkbox and thats all fine and dandy, but now how can I tell how many license seats I am using?  Previously it was driven off the number of users in the jira-users group, but now with the ability to disable users, they seem to remain in the group so the number doesn't decrease.  Is there a new area this information is communicated? 

  23. Anonymous

    The instructions for deactivating an account are wrong. When I edit a user, the only values I get are name and email address. There is no "active" checkbox or anything. I am the account administrator with all permissions. It is not at all clear how I can deactivate a user.

  24. Anonymous

    I also would like to deactivate a few users but the "active check box" is not present where the documentation says it should be.  I thought I had a down-rev version but I'm on 6.0 and the comment that had it was on 5 so how do I activate the activate check box?

  25. Hi, we have a JIRA license (for 10) and a Confluence license (for 50). I'm trying to see who the JIRA users are to figure out how many licenses I have left. When I look at the list of JIRA users though it lists all the Confluence users. Is there a way to see who the Confluence licenses are assigned to and who the JIRA licenses are assigned to? Thanks.

  26. Raj

    Just installed JIRA V 6.2 , Connected to LDAP without any issue , however users are not able to log in. What am I missing ?

  27. Hi,

    we are using JIRA ondemand. I can access only the external user management. But how can I create/edit/delete user properties?

    on this page you write: "but you can still assign users to project roles, and create/edit/delete user properties."... but how?

    Thanks,
    bernd