I have an issue type with 13 custom fields. I need to export the issues with all the custom fields and with the relevant system fields (issue type, summary, description, etc.)
When I run the query and then export with Export --> Excel (Current fields)
some fields are missing.
I've also tried the add-on Better Excel Plugin for Jira (BEPJ), but also with it some fields are missing.
I can do Export --> Excel (All Fields) (which is also available in BEPJ) but then I have to perform a massive clean-up on the resulting Excel file to remove a large number of irrelevant fields.
It seems to me that the Jira API which is invoked by the built-in export (and probably is also used by BEPJ) is buggy.
I am on Jira 6.4.11 and I cannot upgrade to a newer version in the foreseeable future.
Anyone seen this? Any workaround?
I can write Python code to extract the data from Jira into an Excel but I prefer to avoid that route for now.
Here's the official answer from the guys at Midori (developers of Better Excel Plugin for Jira):
This problem is related to Jira's behavior, not to our app's functionality.
Please check these pages:
Exporting column ordered issues
Midori Software Engineer
OK, after digging deeper, I found the reason - the Export-->Excel (current fields) takes the columns from My Defaults instead of from Filter, as shown below.
However, I did not find any way to force the export to use the Filter option.
Using the BEPJ export, all fields are exported when the query finds 2 issues.
If I change the query to find more than 2 issues, it reverts to using My Defaults and only 20 fields are exported to the Excel file.
Just to let people know - due to the problems and complexity of exporting to multiple CSV files and then merging them together (since Jira limits a query to 1000 issues), I have switched to using JIRA REST-API to retrieve all the fields into multiple JSON files.
If you need a CSV as the final outcome, this thread is still for you.
But, if you, like myself, need to get the data, process it and then take it elsewhere, please see my posting here: https://community.atlassian.com/t5/Jira-Core-articles/How-to-export-issues-and-their-links-via-JSON-instead-of-CSV/ba-p/940548
The problem is not with the custom fields but rather with system fields such as Description, Priority, etc.
As I said, in the issue navigator I see all fields that I marked; the export omits some.
To your question, I did not check all fields, but those that I did have the default searchers.
Ugly workaround for now (I have 26 fields total):
1. Export all issues with Better Excel - I get 20 fields (including Key) --> save in A.xlsx
2. Change columns, select Key + 6 fields that are missing from #1 --> save in B.xlsx
3. Copy A.xlsx --> C.xlsx
4. Open B, copy the 6 columns to cliboard
5. Open C, paste using "Insert Copies Cells"
6. Voila! C.xlsx has all columns
I think my user is having the same/related problem. Would someone mind confirming?
1. User "A" created a filter.
2. User "A" exports that filter to Excel and the columns are correct
3. User "B" exports that same filter to Excel & G Sheets but the columns are different and in a different order from what User "A" has.
The problem is present when I tested it using my admin login too. Insights? Fix?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event