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
Currently, the Board endpoint is specific for a repo, so in order to get the full Board data you will need to make one request per connected repo.
There are two options to get the Board data for specific assignees:
Fetch the Board data for each repo and use the GitHub API to fetch the assignee’s data for each issue in the Board.
Fetch the issues assigned to a particular user (this endpoint is also per repository) and then fetch the ZenHub data (current pipeline, estimate, epic status) using the ZenHub API (get issues data endpoint).
The second alternative is best if you only need to do this for one particular assignee, the first one will be more efficient if you need the same information for several assignees.
@ambynair commented on Tue Mar 21 2017
@ambynair commented on Tue Mar 21 2017
I could use curl and get JSON for zenhub board a specific repository.
How do I get the same with multiple repository and for a specific assignee
Something like this ?
curl -H 'X-Authentication-Token: 'xxxxxx' https://xxxx.xxx.com/p1/repositories/repid1+repid2/board/user/assignees
This works for single repository
curl -H 'X-Authentication-Token: 'xxxxxx' https://xxxx.xxx.com/p1/repositories/repid1/board
@pnavarrc commented on Tue Mar 21 2017
Hi, Pablo from the ZenHub team here.
Currently, the Board endpoint is specific for a repo, so in order to get the full Board data you will need to make one request per connected repo.
There are two options to get the Board data for specific assignees:
The second alternative is best if you only need to do this for one particular assignee, the first one will be more efficient if you need the same information for several assignees.
The docs for the endpoints mentioned above:
I hope this helps you!
@ambynair commented on Tue Mar 28 2017
ok, thanks. that was my plan b. Will go with option 2.
The text was updated successfully, but these errors were encountered: