-
-
Notifications
You must be signed in to change notification settings - Fork 469
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
Pagination support for GetIssuesForSprint #302
Comments
Hi! Thank you for taking the time to create your first issue! Really cool to see you here for the first time. Please give us a bit of time to review it. |
This issue has been automatically marked as stale because it has not had recent activity in the last 60 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Hey, I am very sorry that this issue has been open for a long time with no final solution. We work on this project in our spare time, and sometimes, other priorities take over. This is the typical open source dilemma. However, there is news: We are kicking off v2 of this library 🚀To provide visibility, we created the Road to v2 Milestone and calling for your feedback in #489 The development will take some time; however, I hope you can benefit from the changes. What does this mean for my issue?We will work on this issue indirectly. Final wordsThanks for using this library. |
Describe the bug
GetIssuesForSprint
returns only the first 50 issues of a sprint.To Reproduce
GetIssuesForSprint
on itExpected behavior
GetIssuesForSprint
should have anOptions
parameter toStartAt
the 2nd page, like #55 describes.Possible Solution
Add an
Options
parameter toGetIssuesForSprint
that allows the user toStartAt
a specific issue number. So that they eventually can crawl all of them until the results become empty.Your Environment
Include as many relevant details about the environment you experienced the problem in
go version
): 1.14.3Additional context
I tried to get a list of all issues in a sprint, but only got a fraction of the whole.
The text was updated successfully, but these errors were encountered: