Hello Matthias,

thank you for your feedback.

We are  calling the getProjectMembers method directly on the GitLab API to determine the list of assignable users for the Assignee drop-down.

So I am unsure what could be changed on our side to help you with your problem.

Regards,

Torsten

Thank you very much for your reply.

I did some additional checking and actually, the getProjectMembers (/members) only returns direct members and not inherited members through ancestors groups as stated here: https://docs.gitlab.com/ee/api/members.html

I believe it would make more sense to use the method at /members/all (https://docs.gitlab.com/ee/api/members.html#list-all-members-of-a-group-or-project-including-inherited-and-invited-members) since this one returns all project members including inherited members, invited users, and permissions through ancestor groups, which any of those could, in theory, get assigned to an issue.

I did try on our project and verified that /members/all returned the results I would expect.

What do you think?

Hello Matthias,

thank you for the deep dive into this issue, this is much appreciated.

We implemented this solution as issue KLAROS-5356, it will be available with the upcoming 5.7.0 release in early November.

Regards,

Torsten