You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to get times for an issue you have to call /repos/{owner}/{repo}/issues/{id}/times
If you do this for alot of issues, it takes literally ages because of the high amount of requests,
In our case it takes ~20 minutes to fetch all times of all issues.
I suggest to introduce a new endpoint /repos/{owner}/{repo}/issue_times,
which returns all issues (or just their IDs) and the times tied to it.
The same for /repos/{owner}/{repo}/issue_labels.
I would find this useful, to reduce API calls and save alot of time, because the backend can prepare such an response really fast.
The text was updated successfully, but these errors were encountered:
Description
If you want to get times for an issue you have to call
/repos/{owner}/{repo}/issues/{id}/times
If you do this for alot of issues, it takes literally ages because of the high amount of requests,
In our case it takes ~20 minutes to fetch all times of all issues.
I suggest to introduce a new endpoint
/repos/{owner}/{repo}/issue_times
,which returns all issues (or just their IDs) and the times tied to it.
The same for
/repos/{owner}/{repo}/issue_labels
.I would find this useful, to reduce API calls and save alot of time, because the backend can prepare such an response really fast.
The text was updated successfully, but these errors were encountered: