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

Pagination support for GetIssuesForSprint #302

Open
fdcds opened this issue Jun 10, 2020 · 3 comments
Open

Pagination support for GetIssuesForSprint #302

fdcds opened this issue Jun 10, 2020 · 3 comments
Labels
needs triage Ticket that needs triage (a proper look for classification)

Comments

@fdcds
Copy link

fdcds commented Jun 10, 2020

Describe the bug

GetIssuesForSprint returns only the first 50 issues of a sprint.

To Reproduce

  1. Fill a sprint with more than 50 issues
  2. Call GetIssuesForSprint on it
  3. 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.

@github-actions
Copy link

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.

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale label Aug 10, 2020
@andygrunwald andygrunwald added the needs triage Ticket that needs triage (a proper look for classification) label Aug 20, 2022
@andygrunwald
Copy link
Owner

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.
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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Ticket that needs triage (a proper look for classification)
Projects
None yet
Development

No branches or pull requests

2 participants