Stefan-19b opened a new issue, #5126: URL: https://github.com/apache/incubator-devlake/issues/5126
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened As a user I want to see the collected information about the PRs of Gitlab in the 'Engineering Throughput and Cycle Time - Team View' dashboard. To show this data DevLake needs information about all authors of the PRs. But in some special cases this user data is not available. In Gitlab this could happen when a project or group has more than 20 members. In this case only the first 20 members are fetched by DevLake because the `page_size` of pagination is set to 20 by default and the other pages are not fetched. So it could happen that the author information of a PR is missing because the user data has not been fetched by the `collectAccounts` plugin. Due to the missing user data, the query of the dashboard would then not show the corresponding PRs. For Gitlab the `members/all` REST API call is used: https://docs.gitlab.com/ee/api/members.html#list-all-members-of-a-group-or-project-including-inherited-and-invited-members The problematic part of the code for Gitlab can be found here: https://github.com/apache/incubator-devlake/blob/dfeec2ea732b90fa90f4cf09e612c756cf8aa679/backend/plugins/gitlab/tasks/account_collector.go#L42 ### What do you expect to happen If a Gitlab project or group has more than 20 members, the `collectAccounts` plugin should retrieve all members using the pagination API. ### How to reproduce Add more than 20 members to a Gitlab project or group and let DevLake collect them all using the `collectAccounts` plugin. ### Anything else _No response_ ### Version v0.16.0 ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
