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

Deleted LDAP user's assigned issues cannot be searched in Issue Navigator even though it shows in Project Overview

      ======== Steps to reproduce =======

      1. Connect JIRA to LDAP directory and sync. (Connector type)
      2. Assign some issues in a project to an LDAP user in JIRA.
      3. Delete the user in LDAP, and sync again in JIRA.
      4. Going to the Project Overview page, the issues tab, we can see that those assigned issues in #2 has become unassigned due to the deleted LDAP user: UnassignedIssue.jpg
      5. If you click on the Unassigned link, it will bring you to the Issue Navigator to see the list of unassigned issues. But the list is empty: Filter.jpg

      ======== Expected Behavior =========

      1. The issue navigator should show the unassigned issues. (previously assigned to the deleted LDAP user)

      Reindexing does not help.

        1. Filter.jpg
          Filter.jpg
          42 kB
        2. UnassignedIssue.jpg
          UnassignedIssue.jpg
          79 kB

            [JRASERVER-34246] Deleted LDAP user's assigned issues cannot be searched in Issue Navigator even though it shows in Project Overview

            Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for the greater customer base. To that end, we aim to keep our issues up-to-date so that they accurately reflect current customer needs.

            Because there has been no customer activity on this issue in a long time, we have marked it as closed. If you still feel that this issue is still relevant to your needs, please feel free to raise a new issue and link to this one.

            Jakub,

            Jira DC Quality Engineering

            Jakub Cegiel added a comment - Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for the greater customer base. To that end, we aim to keep our issues up-to-date so that they accurately reflect current customer needs. Because there has been no customer activity on this issue in a long time, we have marked it as closed. If you still feel that this issue is still relevant to your needs, please feel free to raise a new issue and link to this one. Jakub, Jira DC Quality Engineering

            These issues are still assigned, to a particular username, its just that there are no accounts with that username in any of our User directories.
            If you view these issues in the View issue page, you will see this.

            So my initial reaction is to say that the Issue Nav is right, and the Project Overview is wrong.
            On the other hand, having issues reported by "phantom" users is probably OK, but having them assigned to phantom users is a real problem for customers.
            They probably want some way to search for deleted users in order to sort this out? Having the Overview show a count of "issues assigned to invalid users" may be useful?
            (it may include deleted and also inactive users?)

            Mark Lassau (Inactive) added a comment - These issues are still assigned, to a particular username, its just that there are no accounts with that username in any of our User directories. If you view these issues in the View issue page, you will see this. So my initial reaction is to say that the Issue Nav is right, and the Project Overview is wrong. On the other hand, having issues reported by "phantom" users is probably OK, but having them assigned to phantom users is a real problem for customers. They probably want some way to search for deleted users in order to sort this out? Having the Overview show a count of "issues assigned to invalid users" may be useful? (it may include deleted and also inactive users?)

              Unassigned Unassigned
              dleng Daniel Leng (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: