Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zenhub API for Board with assignee #5

Open
kamis3ci opened this issue Sep 9, 2017 · 0 comments
Open

Zenhub API for Board with assignee #5

kamis3ci opened this issue Sep 9, 2017 · 0 comments

Comments

@kamis3ci
Copy link

kamis3ci commented Sep 9, 2017

@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:

  1. Fetch the Board data for each repo and use the GitHub API to fetch the assignee’s data for each issue in the Board.
  2. 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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@kamis3ci and others