I would suggest looking over the following documentation and issue, since I ran into the same issue, which turned out to be this:
I'm really sorry, I meant "tools", with the little cog.
Have a look at https://confluence.atlassian.com/display/JIRA/Using+Filters- there are some screenshots there along with better written guidance than I can give.
I'm not sure how else to say it. There's a significant difference between "what user has chosen to see" and "filter column order".
Here's a quote from the page you linked to:
To add a column layout to a saved filter:
If I do this, and add a column that happens to be a custom field, it is not saved as #4 says it will be. It disappears as soon as I refresh the page. I also don't think the sorting works on a custom field (at least, not if you try to refer to the field by its name).
I have the same issue. I have a filter owned by me. I can modify the query definition and save the modified filter. I can add and remove columns, but for some columns, as soon as you refresh the filter (click the "Search for Issues" icon), the added column dissapears from the filter, and so impossible to save the filter with these columns.
I added the columns to "Filter", not to "My Defailts" or "System"
I have the impression adding columns works with 'system' columns, but not for (some type of ???) custom columns. Did not find out yet what kind of columns cause problems.
This could also be that the columns aren't valid for part of your query, so Jira is hiding them. Can you check that fields that are vanishing have a "global" context? They belong to ALL issue types and ALL projects? (Even if they aren't on screens)
This is a long-standing and frustrating design failure in Jira.
Thanks for posting this... I saw the same problem and wasn't able to figure out why columns were sometimes saved, but not other times. Once I started referencing the columns in the query (even if I didn't really want to filter by those columns), they persisted. Bad design...
Referencing the field in the query excludes issues for which the field is not valid. They will, of course, always show up then, but you could be losing issues from the filters intention. You need to check the validity of the columns - they ARE being saved, but because of this flaw in the design, they get hidden.
Nic, sure, you SHOULD narrow the search only to issue types and projects that the field is valid for. But we do often do wide searches, including many issuetypes. It seems that in such case adding "AND (your_column is empty OR your_column is not empty)" is the only way to have your column in the filter AND show wide issuetypes palette.
Hi Nic, thanks for your answer. Indeed, these columns do not have a "global" context. They are only used in 1 project, the filter starts with "Project = XYZ...".
It's nice you call this a "long-standing and frustrating design failure"... I would call it a rather basic high priority DEFECT. Very, very very.. frustrating indeed.
Is this "behaviour" documented somewhere ? Do you know if issues are already registered for this (so I can add my useless vote to them :-)) ?
Yeah, I'm trying to be nice, avoiding the bad words I really think about it, and call it a "design failure" because I'm not sure it's technically a "defect" (it's designed that way. I reserve my bad words for whoever thought that was a good idea) Watch/comment/vote on https://jira.atlassian.com/browse/JRA-9367
However if you're using Project = XYZ, it's not that problem.
Could you step through exactly what steps you're doing though, as you change the columns? I had a user who was going "add column, click save to return to the filter, click refresh to reload it, then complain that columns were missing" - because he'd not saved the changes to the filter, he was effectively reloading the current copy, which, of course, didn't have his column changes in it. (He needed "add column, click save to return to the filter, click save to save the filter, click refresh to reload it, then not complain that columns were missing" )
It's not a "design failure" nor a "defect" but a hook to make money. Now, instead of complainnig against JIRA and report incidences, everybody can buy the solution to "Show Saved Filter with Columns" ( https://marketplace.atlassian.com/plugins/com.ja.jira.plugin.searchrequest).
I did not only limit the custom field to the particular project, but also to one issue type. When I started the filter with "Project = XYZ AND issuetype = abc...", I was indeed able to add the custom field in the filter output.
I understand now. But we have 500 people using Jira, THEY do not know (and can not know) how exactly the custom fields are defined, and so how they should construct their filters. Very complicated to explain them all the cases.
Thanks anyway for your quick clarification!!! (you should join Atlassian lol)
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot