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; } } }

Default columns in private filter do not "stick"

Bryan Young_6wbnud

I created a private filter and made it one of my favorites. I then configured the My Defaults columns under the Columns button. However, when I re-run the search or leave the page and return, it always reverts to the original set of columns and I have to click "My Defaults" again to get the view I want. Assuming I'm not an idiot, it would seem Atlassian doesn't understand the meaning of the word "default".

Accepted answers

Bryan Young_6wbnud

I found my answer under "related community content", but it doesn't look like I can delete my question. If you're here, the answer is to change the columns under the "Filter" tab instead of "My Defaults".

All comments

Bryan Young_6wbnud

John Funk

Thanks for posting the answer. And no need to delete the question - it will help someone else in the future. :-)

Avri Burger

I'm not so sure the answer above is an actual answer as much as it is a workaround—an unnecessary one at that. Let me explain: I'm currently having the same problem, which wasn't present on Jira Server and I seem to recall not even having this problem last week. So I tried logging into Jira from an incognito window and it turns out the My Defaults tab was active as soon as I viewed filtered results. This seems to point to a cached data issue. I cleared my cache and cookies for Jira and Atlassian and the issue persisted, so I cleared my browsing history, cached images and data, and site data for the last 7 days, then deleted my atlassian.net and atlassian.com cookies and that did the trick. I have no idea if this won't happen again, but if it does, this is what I will do again. As for WHY this happens? *shrug*

[UPDATE]

The next day (today) when I logged in, the columns were back to their old shenanigans, so I had to go through the whole process again. This solution is less than optimal, but highlights that this is a problem with something persisting in the cache, cookies or both. Unfortunately for me, it is the only solution available as I am unable to modify which columns I see in the standard filter.

Dimitris Kesanlis

The point of 'My defaults' is that we can export csv quickly with the prefered columns. With export csv you have 2 options. Either export with all fields (375 in my case), or with My Defaults.

Export csv (all fields) is not practical.

We should be able to either export with filter fields, or save a My default columns configuration (which again, is not optimal, because different projects use different fields, etc.)

edit: I don't know how it happened, just now I saw that there is an option export csv (filter fields).