nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CSV Export not exporting saved filter columns

Sysaccount

I am using Jira cloud, I recently created 10 filters and gave permissions for the teams to access the filters(i.e. 10 filters for 10 teams). The teams are able to view the columns saved for the filter in the issue navigator view but when they export they are not getting the default fields instead of saved filter columns.

This functionality is inconsistent, sometimes it exports the right columns, sometimes it exports the default columns.

Any Jira experts out there to help me on this?

Accepted answers

All comments

Brant Schroeder

In the dropdown menu to export there should be two options. Export "type" (All fields) and "type" (Current fields). If a user selects the current fields option, it will create an export for the issue fields that are currently displayed in their Issue Navigator. My guess is that they are selecting different exports each time and that is why they are seeing different results.

Kristina Haggård

We have the same issue with the export thingy, starting a couple of month back with export to Excel, now that Excel is not an option anymore, the same issue with the CSV.

The columns that I select are selected.

The filter is saved.

The result is arbitrary I must say. Some selected columns are there, but not always. Changing the selected columns does not change the outcome at all.

So I would say this is a bug, that must have been introduced around fall 2017 as it started to appear then. Before that the export worked nicely.

Kristina Haggård

@Brant Schroeder, sorry, forgot to mention you in my previous comment.

Brant Schroeder

Are you on cloud or hosted?

Subbu_wl2cbi

Selecting export of current fields option is important. I still had very inconsistent and random results that drove me crazy. What really helped is clearing the browser cache. For the cache period, you might want to go back in time as far as the point in time when you last modified the filter JQL.

Michael Garvais

Is there a real answer for this? We are also seeing very inconsistent results on export.

Subbu_wl2cbi

I see consistent behavior as long as I do not execute a filter that I just edited. If you have to edit a filer, I suggest you save it, (and may be clear brower cache) and then execute the saved filter.

Sarah Oros

This is happening to me too, even after clearing my cache.

Kristina Haggård

I found that chosing the right tab while exporting might be the key. There are 2-3 tabs to pick from (dont remember their names.. ). If you pick the right tab AND chose to export visible columns only, Jira will do its thing. (Server version)

paula.white

Happening to me too in the Cloud version - sometimes it works and sometimes it doesn't - very frustrating!

Cree Myers_ztvsla

Here's an old (open) issue related to this that's getting several new comments complaining about current occurances. https://jira.atlassian.com/browse/JRACLOUD-69193

Seems like a lot of people are impacted. How can we get JIRA's attention. They must have broken something in a recent update.

Cora Middleton

As of 2022-10-18 this is still broken for me on Jira Cloud, and I've eliminated the possibility that this is a browser caching issue (used different browsers for create/edit and export, respectively). This makes even simple analysis untenable.

Jhan Knebel

Oh look, 2024 and this is still an on again/off again issue! Seriously Atlassian, can you please stop adding and removing things at will? I HATE that I can't rely on your product to work the same time each time I log in.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

csv

jira

cloud

jql

filter

export