Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Does exporting filter results to Excel has a limit of number of fields?

Amir Katz (Outseer)
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 28, 2018

I created a filter and configured the columns I want to see (total of 21 columns). When I run it, I get the issues and I see all my columns.

However, when I do Export --> Excel (Current fields), one of the fields, Descriptionis not in the Excel.

I removed one column (Status) and now I see the Description.

However, I need all the fields since I will use the file to import the issues into another project on another Jira instance.

It sees there a limit on the number of columns to 20. Is this a bug or a documented limitation?

Jira version is 6.4.1.

Thanks, Amir

1 answer

0 votes
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 2, 2018

Hey Amir,

I was unable to reproduce this issue in Jira 6.4.14 and didn't find any bugs related to this between 6.4.1 (your version) and 6.4.14 (where I tried to reproduce). I was able to get 26 columns in the export I attempted.

The 6.4 branch has had many bugfix releases since 6.4.1. They're all out of our general support window now as well - I'd recommend upgrading to 7.2 (minimum supported version) or above to take advantage of all the new features we've developed and to get into our standard support window. We officially support versions for two years after their initial release. If that's a high-risk situation for your environment or you're out of maintenance, I'd at least try and get up to 6.4.14 to take advantage of the 140+ bugfixes since 6.4.1.

I can't think of any plugins off-hand that might affect the number of columns you can do an export on, but it might be worth seeing if that might be an issue. If you have a test environment available, try putting Jira in safe mode (to disable all plugins) and see if you can reproduce the problem. If the issue goes away, there is a misbehaving plugin. Otherwise, I would suggest working on an upgrade.

Cheers,
Daniel

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events