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
GetIssuesForSprint returns only the first 50 issues of a sprint.
To Reproduce
Fill a sprint with more than 50 issues
Call GetIssuesForSprint on it
Find that only the first 50 issues are in the result
Expected behavior
GetIssuesForSprint should have an Options parameter to StartAt the 2nd page, like #55 describes.
Possible Solution
Add an Options parameter to GetIssuesForSprint that allows the user to StartAt 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-jira version (git tag or sha): v1.12.0
Go version (go version): 1.14.3
Jira version: JIRA Cloud
Jira type (cloud or on-premise): JIRA Cloud
Involved Jira plugins: None
Operating System and version: Linux 5.16
Additional 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:
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.
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.
If you seek priority development for your issue + you like to sponsor it, please contact me.
What does this mean for my issue?
We will work on this issue indirectly.
This means that during the development phase, we aim to tackle it.
Maybe in a different way like it is currently handled.
Please understand that this will take a while because we are running this in our spare time.
Final words
Thanks for using this library.
If there is anything else you would like to tell us, let us know!
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: