Is it possible to export all issues in the On-Demand version of JIRA? i see only 1000 issues can be exported and we have approx 6000...
Can be quite time consuming merging into one file for reporting.
According to the below it appears not possible,
also tried, increading tempmax value in URL, but still a no go.
No, you can't export them this way.
The only real way to do it is to create a backup and download it, then extract the data you need from the raw xml. Which is very complex.
However. As you've mentioned you are doing this for "reporting", you might find it more useful to look at what the reporting is doing. Most of the cases where someone has asked me for "a copy of everything", they've ended up with reports that are, at best, useless, and in most cases, downright wrong.
Could you tell us what reporting you are actually looking for? There's a good chance Jira can either tell you itself, or one of its reports can give you a much better start than "show me everything"
Thanks Nic for the quick reponse.
Obviously we have x amount of issues, and we get user requests for this and that field etc...
I'm trying to populate a report, so we can actually see what fields are in use in the system, and what are not.
Originally during initial setup, there were a lot of fields added... some may not have been used, so we're trying to keep it streamline and see what we cna remove.
Yes, that makes sense. However, it's a one-off housekeeping exercise - that does sort of lend itself to a quick grab of all data, but as that's quite difficult here, I'd try a different approach, one with a bit more human analysis
First, nip into the list of all your custom fields and take a copy of all their names. That simply gives you a list of fields you want to check.
Secondly, remove any from the list that you already know you want to keep. No point in looking at them, you know you want them.
Third, the boring bit. Go to "search for issues" and then the advanced search. For each field you want to check, use the JQL "<field> is not empty".
If you get a high number of results, the field is being used a lot. If you get no results, delete the field because no-one is using it. If you get a small number of results, then you'll need to investigate further, it might be junk, or genuine.
I regularly (Bamboo build) export issues from JIRA OnDemand to a local database for reporting in Confluence. In my case it is just a few thousand and I have scripted it for performance. I simple way of doing this that probably is sufficient for your purposes is just using csv: How to export JIRA issues to CSV
Yes, I believe others have done that. I seem to remember having to specify the proxy parameters on the java command (in your jira.sh or atlassian.sh file start file). A quick reference to this post suggests something like:
I tested this from a local test instance we have and the tool would fit our purpose, however i don't think it will work with our OnDemand due to proxy issues and including all available parameters in the command line tool results in same issue below
Cause: ; nested exception is:
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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