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

[Bug] API getSprints needs an extra query param startAt for when we have more than 50 sprints #75

Closed
1 task done
jmkhael opened this issue May 11, 2023 · 1 comment
Closed
1 task done
Assignees
Labels
bug Something isn't working

Comments

@jmkhael
Copy link

jmkhael commented May 11, 2023

Describe the bug
When a given board has more than 50 sprints already (which is the cap of maxResults), there is no way to go beyond that.
JIRA API accepts a query param startAt

To Reproduce
Steps to reproduce the behavior:

  1. Call the API with a board id having more than 50 sprints,
  2. notice you cannot go past that max

Expected behavior
Be ble to paginate results with the help of startAt query param.
This would get resolved into a ReST request equivalent to:
https://jira.domain.com/rest/agile/1.0/board/3236/sprint?maxResults=50&startAt=100

Plugin version and platform

  • Version: latest
  • Obsidian Windows
@jmkhael jmkhael added the bug Something isn't working label May 11, 2023
marc0l92 added a commit that referenced this issue May 30, 2023
Implement paging offset in the plugin api #75
@marc0l92
Copy link
Owner

Thanks for reporting this issue, the fix has been released in version 1.53.0

@marc0l92 marc0l92 closed this as completed Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants