Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34563

Deleted LDAP User cannot be removed from Project Role

XMLWordPrintable

      Steps to Reproduce

      1. From LDAP, delete a user that has been added to a project role in a JIRA project.
      2. Attempt to remove the user from the project role in JIRA. JIRA returns an error that the named user cannot be found. The user doesn't appear to be removed from the Project Role.
      3. After a restart the user seems to be removed from the project role, but the bad role is still present in the database; it just fails to load with an error message in the log.

      Workaround

      1. Add the user to the internal directory.
      2. Delete them from the project role.
      3. Remove that user (it's recommend to deactivate them instead as per Managing Users).

            [JRASERVER-34563] Deleted LDAP User cannot be removed from Project Role

            Keith added a comment -

            This was not resolved.

            Keith added a comment - This was not resolved.

            David Holshouser added a comment -

            This has happened on my Jira 7.2.1

            Version 7.2.1
            Build Number 72003
            Build Date Wed Aug 31 00:00:00 MDT 2016
            Build Revision 3448e6b44e2f47d5328e04b682d181ed99b88ec2

            David Holshouser added a comment - This has happened on my Jira 7.2.1 Version 7.2.1 Build Number 72003 Build Date Wed Aug 31 00:00:00 MDT 2016 Build Revision 3448e6b44e2f47d5328e04b682d181ed99b88ec2

            Intel CHD Jira Admin added a comment -

            Hi Oswaldo,

            It is incorrect that the bug is classified as minor. It is a major problem for us to communicate the problem to the user community and provide a workaround for them when they hit this case. And then we have to go to the expense of upgrading to 6.1.1 soon after the expense of upgrading to 6.0. Atlassian should be more careful in regression testing.

            Regards,
            David

            Intel CHD Jira Admin added a comment - Hi Oswaldo, It is incorrect that the bug is classified as minor. It is a major problem for us to communicate the problem to the user community and provide a workaround for them when they hit this case. And then we have to go to the expense of upgrading to 6.1.1 soon after the expense of upgrading to 6.0. Atlassian should be more careful in regression testing. Regards, David

            Benjamin Copeland added a comment - - edited

            David, it did not work for me that way...

            When I create the user the user name adds a #1 to the end of their username. If I rename my newly created internal user to #1, then it renames to #1#1.

            I then deleted the user from the internal dir and it removed the user from project roles.

            Benjamin Copeland added a comment - - edited David, it did not work for me that way... When I create the user the user name adds a #1 to the end of their username. If I rename my newly created internal user to #1, then it renames to #1#1. I then deleted the user from the internal dir and it removed the user from project roles.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi zeilush,

            I understand this issue is a major problem for big companies.

            Having said that, given the number of issues we need to triage the priority field is set according to a standard as specified in https://jira.atlassian.com/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels

            Additionally, you can review the priority in the original bug reported for this problem JRA-25220 which was set to "Minor" as well.

            Nevertheless, this problem is a regression of a bug we had already fixed on a maintenance release, so we are keen on getting a fix for it soon.

            At the moment, I can't give you precise dates for this, but please feel free to watch the issue for status updates, as it will be updated as more information becomes available.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi zeilush , I understand this issue is a major problem for big companies. Having said that, given the number of issues we need to triage the priority field is set according to a standard as specified in https://jira.atlassian.com/secure/ShowConstantsHelp.jspa?decorator=popup#PriorityLevels Additionally, you can review the priority in the original bug reported for this problem JRA-25220 which was set to "Minor" as well. Nevertheless, this problem is a regression of a bug we had already fixed on a maintenance release, so we are keen on getting a fix for it soon. At the moment, I can't give you precise dates for this, but please feel free to watch the issue for status updates, as it will be updated as more information becomes available. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            PeterL added a comment - - edited

            Hello,

            why is this bug treated as minor?

            Administrators can't edit the roles of a project roles while a deleted user appears in a project role.

            A restart of a jira is a no go in big companies.

            PeterL added a comment - - edited Hello, why is this bug treated as minor? Administrators can't edit the roles of a project roles while a deleted user appears in a project role. A restart of a jira is a no go in big companies.

              rtekhov Roman Tekhov (Inactive)
              takindele Taiwo Akindele (Inactive)
              Affected customers:
              8 This affects my team
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: