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

User Without Group Membership In Delegated LDAP listed in the Assignee Field

XMLWordPrintable

    • 4.04
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 06 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      User without any group membership appear in the Assignee Field.

      Steps to reproduce:

      1. create a new group called "testgroup"
      2. create a user called "vicky" in the Internal Directory. Associate the user to group "testgroup"
      3. in the Permission Scheme, associate the group "testgroup" to the Assignable User permission.
      4. create a new issue and try to assign it to the user "vicky". Issue can be assigned to "vicky".
      5. create the Internal with LDAP Authentication directory
      6. create a new user called "vicky" in the delegated directory. This user not member of group "testgroup"
      7. arrange the directory sequence so that the delegated directory on top
      8. in the user list, user "vicky" from the delegated group will not have the group "testgroup"
      9. create a new issue. Then, try to assign to the user "vicky". Vicky is listed in the Assignee field. But, it will throw error that "vicky" can not be assigned.

      From the test, it's seems that the Assignee field is retrieving the user "vicky" from the internal directory instead of the delegated directory.

        1. Assignee.png
          Assignee.png
          87 kB
        2. DelegatedUser.png
          DelegatedUser.png
          37 kB
        3. DirectorySequence.png
          DirectorySequence.png
          41 kB
        4. ERROR.png
          ERROR.png
          74 kB
        5. InternalUser.png
          InternalUser.png
          39 kB

            [JRASERVER-29053] User Without Group Membership In Delegated LDAP listed in the Assignee Field

            Evelin added a comment -

            For us, this is no minor problem. The users that have left accumulate in the Assignee list. People are complaining about that, and the list grows longer and longer.

            Evelin added a comment - For us, this is no minor problem. The users that have left accumulate in the Assignee list. People are complaining about that, and the list grows longer and longer.

            Eric Dalgliesh added a comment -

            The behaviour for select-for-field and be-valid-for-field should certainly be consistent.

            Eric Dalgliesh added a comment - The behaviour for select-for-field and be-valid-for-field should certainly be consistent.

              Unassigned Unassigned
              jalbion Janet Albion (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: