Very close.. about gitlab-time-report

[insolite]

Spent hours are fetched after fetching issues since GitLab API does not provide time fields in issue response data in any way at the moment. But I see there is even no issues count data, so that looks like the pagination issue I was experiencing recently. The GitLab API provides pagination with max 100 items per page. It's kinda difficult to implement pagination using redux-api-middleware so I'm thinking about migrating to some kind of "pure promise middleware" and implement pagination support from scratch. So some issues might be lost at the moment if they are not filtered enough.

[insolite]

As a partial temporary solution, you may try to apply filters and press "refresh" or reload page (with URL query string args). Then data should be fetched with filters initially and if resulting issues count is less than 100, everything should display properly. I hope I'll fix it in a week or so.

[mitchiru]

Thx for feedback!

I tried the filters and also the pagination is not an issue since I have only one ticket with spend time. But even with filters on it fires about 145 requests.

I can see the only ticket available within the filtered project - but still no time reportings

[insolite]

Seems like I forgot how it works, sorry 🙂. As for 145 requests with filters: yep, that's my fault, fixed it in commit above. Also need to make an edit here. The only filter that will affect server requests count is "project". Members and milestones can't be applied on API level as well as I know.

Well, now there is at least an issue. But I still can't realize how can time stats be lost when issue is present. You're right, that's definitely not a pagination issue. If it is possible could you please provide /projects, /projects/*/issues and /projects/*/issues/*/time_stats responses related to that issue? Or simply store's state ($r.store.getState(); - available with react dev tools) if you can. That would help a lot but if there is something confidential then it's ok, I'll try to debug it on my own.

[mitchiru]

You can have my config.jsx :-)

export const GITLAB_URL = 'http://tglc.de:81';
export const PRIVATE_TOKEN = 'u7F5egDgLZBny8zStX89';

redbulll winglab is the project where is one issue at my name, which should have an spend time of 5m

[mitchiru]

btw pull fixed the 145 requests but issues are now gone.

[insolite]

Wow, thanks a lot! I see two projects with the same name (39 and 41 IDs). Can it be a reason for disappeared issues? I've selected both of them and see the issue you mentioned before from 39th project. Also time stats are OK.

http://127.0.0.1:3030/#{"projects":[39,41],"members":[3]}:

[mitchiru]

wow.

hm there is def only one project with this name. maybe one deleted?

[insolite]

Do you mean archived field? It's false for both. Btw 41th is in another namespace.

[insolite]

I've implemented pagination support and also made time stats retrieving from issues response as it seems like they added a time_stats field to issues API in one of latest GitLab versions. So everything for your case should be OK now.