• We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      we've had several contractors leave lately and their userid's are in the system; I can't delete them because they're listed as the assignee on closed tasks. I can remove them from all groups, but they still show up in user listings even though they're not "active", and I can't erase the email address (which is no longer valid) from their account

            [JRASERVER-931] need ability to 'disable' users without deleting

            Hello we have a similar problem - however we also have a user allocation that we pay for, if we remove users from groups, do we still end up paying for them on a monthly subscription even though we have effectively deactivated them?

            Louise Lister added a comment - Hello we have a similar problem - however we also have a user allocation that we pay for, if we remove users from groups, do we still end up paying for them on a monthly subscription even though we have effectively deactivated them?

            bain added a comment -

            In our documentation (http://confluence.atlassian.com/display/JIRA/Managing+Users) we suggest that you remove all groups from the user to deactivate them. There is a "feature" in JIRA that allows "System Admins" and "Admins" to login to even if they are not "JIRA Users". This is to get around a common situation in support when customers locked out all JIRA admins (by removing 'JIRA User' from their admins). So basically, you have to remove a user's use permission and its 'admin' or 'system admin' privileges. The easiest way to do this is to remove them from all groups.

            bain added a comment - In our documentation ( http://confluence.atlassian.com/display/JIRA/Managing+Users ) we suggest that you remove all groups from the user to deactivate them. There is a "feature" in JIRA that allows "System Admins" and "Admins" to login to even if they are not "JIRA Users". This is to get around a common situation in support when customers locked out all JIRA admins (by removing 'JIRA User' from their admins). So basically, you have to remove a user's use permission and its 'admin' or 'system admin' privileges. The easiest way to do this is to remove them from all groups.

            Hi All,

            The best way to browse only users have access to your JIRA instance is to do the following:

            1. Login to JIRA as an Administrator, and click on "Administration" (from the menu across the top)
            2. Click on "Global Permissions" (from the menu on the left)
            3. Note down which groups have the permission "JIRA Users, Ability to login to JIRA. They are a 'user'. Any new users created will automatically join these groups.Note: All users need this permission to login to JIRA, even if they have other permissions." NOTE: By default this is the group "jira-users", if you have more than one group listed then you will need to perform more than one filter (this may be possible with JQL the new search functionality coming out in JIRA 4.0)
            4. Click on "User Browser" (from the Admin console)
            5. In the top right is the filter "In Group"
            6. Select the group you noted down before for the value of "In Group" (most likely "jira-users")
            7. This will show you only users that have access to login to JIRA

            Hope this helps,
            -Roger

            Roger Symonds added a comment - Hi All, The best way to browse only users have access to your JIRA instance is to do the following: 1. Login to JIRA as an Administrator, and click on "Administration" (from the menu across the top) 2. Click on "Global Permissions" (from the menu on the left) 3. Note down which groups have the permission "JIRA Users, Ability to login to JIRA. They are a 'user'. Any new users created will automatically join these groups.Note: All users need this permission to login to JIRA, even if they have other permissions." NOTE: By default this is the group "jira-users", if you have more than one group listed then you will need to perform more than one filter (this may be possible with JQL the new search functionality coming out in JIRA 4.0) 4. Click on "User Browser" (from the Admin console) 5. In the top right is the filter "In Group" 6. Select the group you noted down before for the value of "In Group" (most likely "jira-users") 7. This will show you only users that have access to login to JIRA Hope this helps, -Roger

            We have the same need. Too much clutter from disabled users.
            We disable them by assigning a random password.

            Bryce Jira Nesbitt added a comment - We have the same need. Too much clutter from disabled users. We disable them by assigning a random password.

            yah, that works. they still show up in the main user list though. might be nice to have a "disable user" which removes them from all groups, and then a "show disabled users" checkbox on the list that would be turned off by default.

            not that big of a deal though.

            Tim Dawson added a comment - yah, that works. they still show up in the main user list though. might be nice to have a "disable user" which removes them from all groups, and then a "show disabled users" checkbox on the list that would be turned off by default. not that big of a deal though.

            Tim,

            Only people with the USE permission can login to JIRA.

            You could just remove them from all groups which have that permission? AFAIK that should render them effectively 'disabled'.

            Cheers,
            Mike

            Mike Cannon-Brookes added a comment - Tim, Only people with the USE permission can login to JIRA. You could just remove them from all groups which have that permission? AFAIK that should render them effectively 'disabled'. Cheers, Mike

              scott@atlassian.com Scott Farquhar
              d32fc554e6cd Tim Dawson
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: