A workaround that works well without having to create a new filter is to remove any extra jql from the URL: your-company-jira-URL/issues/?filter=1234

Then the export will work

Found a work-around.  Do a Save As for the problem Filter and the new Filter exported the Filter Columns as expected.

Work-around doesn't work - it's impossible to save the ordering I want.

Ever time I set Columns -> My Defaults (instead of the default of Filter) and then go to save filter, it saves it with the default Filter ordering!

Worked fine last Fri - just started happening this week - am checking with our company's Jira support. But it seems unlikely that my issue would be the same as what was reported in 2013 :/

We are seeing this behavior in Jira 8.5.1 when exporting to CSV (current fields) from a saved filter.

Hello Team,
As a release manager, I am required to manage multiple releases and get details from dashboards of multiple PM's on multiple projects. Now every PM as per their requirement create queries and filters. Now, if I have to collate all the details and pull data from each query; its practically not possible for me to first create duplicate query with my filters... its sheer duplication of effort and waste of my time. Thus, having a simple fix, i.e. to export the data as per the column view selected. Though this looks like a small fix, please consider this with higher priority coz, most of the people here will be facing a similar issue. Thus, can you please increase the PRIORITY to HIGH for this requirement and address the same ASAP.
Thanks,
Best Regards,
Manish Gupta
Release Manager
Thomson Reuters

Our users are also experiencing the same issue. However it is slightly different. They were trying to extract someone else’s report. Though “My Default” was selected JIRA extracted the fields selected by the filter creator.

Another workaround may be to use hardcoded column configurations in Excel templates and export those with the Better Excel Plugin. It basically decouples the exported columns from the currently visible columns in Issue Navigator.

If you have a few (fixed) column configurations that you export frequently, it may be great. If you want to export lots and lots of different column configurations, then it may be impractical.
Anyway, this is an option to be aware of.

If you are using a shared filter you lose the filters columns when you save as. So the work around does not solve the problem when you are using a shared filter.

Workaround - save the filter again

Hi shauth,

That does seem very strange indeed, and given the old version it could be something that is fixed by the upgrade.

If you do see the issue again after upgrading to the latest JIRA, could you please create a support ticket at https://support.atlassian.com? We should be able to troubleshoot further with you there if necessary.

The credentials should be the same as for this site (https://jira.atlassian.com).

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].