Adding paging
- CLI now returns help rather than an error when passing no args.
- Adding paging so that latest sprints are returned.
FWIW, if the goal of jiractl is to provide a CLI for the JIRA API, I'm :-1:, because this is adding a custom metric to the results of the JIRA API.
I can imagine, however, the many users would want to add their own custom metrics. As an alternative to adding them all to jiractl, is there a pattern or a way to extend/wrap jiractl? Can you add customer commands / metrics by leveraging the JSON output?
The initial goal was not to build a CLI for the JIRA API. It was to move common developer interactions with JIRA away from the overloaded UI to a simple, quick CLI. I would say that having a velocity view at all implies that an intention of jiractl is to analyze team metrics, which should include other agile metrics.
All of that being said, it might still make more sense to move this change to epic watch as it will get way more use there and better integrate into our current workflow.
I plan to split this PR so that we can get the other improvements merged and we can consider adding predictability to here, epic watch, or both.