Accessing Sprints from GitHub / synchronizing with GitHub Milestones

Our team finds it unfortunate that Milestones support is being deprecated. It was very convenient to be able to access issues assignment both from GitHub and ZenHub. Now, it appears to be impossible to understand Sprint definition from GitHub.

Did anyone figure out a workaround to sync the content of ZenHub Sprint to a GitHub Milestone? I am thinking it should be possible to have a script that goes over the content of a Sprint using ZenHub API, and then assigns the Milestone with the same name using GitHub API.

Today we discovered that when we look at the closed issues in the past sprint, clicking “Load more issues…” at the bottom of the list does not change the content of the list, and does not disappear after being clicked. And unfortunately, there is no way to check in GitHub interface whether what is shown in ZenHub is correct or or not.

2 Likes

Is it too much to ask to hear the thoughts about this from ZenHub developers?

1 Like

Hi all! Not a developer, but I get to work with them a lot! What I’ve seen/ heard is the time saving benefits from the automation that sprints offers, as well as improvements with the reports. Being able to track unfinished work and the auto creation/closing has been incredibly helpful.

Right now- we do not have an API endpoint for sprints, but it is something our team is investigating! You can add your thoughts on our productboard: API updates - ZenHub Portal | Product Roadmap

I’m curious, are your teams using the ZenHub extension?

1 Like

Quick tip - if you’re looking for a list of issues that were closed in a Sprint, go to the Burndown report, select the Sprint you want, and then scroll down.

There’s a Sprint report under the burndown that you might find useful…

2 Likes