I expect the below line to return about 2000 issues, but when I run it it returns on 400, it there a way to bump up a limit to say 3000.
./jira.sh --server https://abc.com --action getIssueList --columns 'key,reporter,assignee,"Auto Lead"' --search "filter = my_filter" --outputFormat 999 --file "/data/jira-next/jira-cli-4.0.0-SNAPSHOT/jira_other_fields.csv"
There are a number of search configurations you need to check before assigning the blame to CLI.
Does a smaller result set return the desired result? You might want to look at the atlassian-jira/WEB-INF/classes/jpm.xml for these few options (or more):
Hope this helps.
The JCLI getIssueList doesn't have a limit (other than your client's java memory setting). It should return all issues that satisfy the filter. There has been a report of a case that JIRA was not returning all the data so a new REST based implementation was added and this did work correctly in that situation. This is documented in JCLI-492. To use the new support use the jql parameter (instead of search) with your direct JQL or using the JQL: filter = "<my filter name>".
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs