[+1] @davidgreens

Ok - we looked at JRA-23005 and resolved that Justin wasn't aware of the functionality that is provided in JIRA - the ability to customise columns when you save a filter. I had got confused by this discussion, and thought Justin wanted something else.

Looks like everyone is happy.

I think having a means to do it with JQL would be a great start - I personally could live without a UI if it meant I could at least customise columns for filters that are intended for a specific audience.

Not sure I follow why you say the UI is the difficult part: the UI to customise already exists, can it not be re-used in an "associated with filter" mode? i.e. If I am viewing a filter which I own (can save changes to), then customising columns is customising for that filter? If I do not have a saved filter open, or invoke the screen from the preferences menu, then I am customising my own column preferences. The same may not be true for the data model representation of a filter; that would need to be extended or rewritten.

Do you think that a JQL style approach would work?

select project, issuetype, summary, description from issues where ......
select defaultColumns() from issues where ....
select savedFilterColumns(1200) from issues where filter = 1200

Or how important is a UI to you? I guess it would be great to have drag & drop columns, but unfortunately I believe that would be a significant rewrite of the issue navigator.

Thoughts?

This feature is sorely missing: it does not make sense to have custom sort orders for filters if you can't also have custom columns. Seems like a simple feature to implement given that projects and users can already specify custom columns. I have raised JRA-23005 instead to cover this - please vote for it!

I agree with Tim. This issue hasn't been resolved, as it was not truly a duplicate of JRA-113. If we could have different filters come with different column selection and sequence, that would be useful!

also, this would need to save the display sequence (left to right) as well as the sort order. I think I may have used the term "order" in both meanings, which might have been confusing.

Yes that's what I'm looking for, along with saved sort orders please.

I'm not familiar with the JIRA codebase or what design approach you're thiking of, but I din't think it would be too complex... I've built several trouble management systems for telecom companies which were similar to JIRA, and the last one I did a few years ago had this feature. we simply defaulted the columns in the search (it would have been too much to place it on the main search screen) unless the user went to an advanced search tab where they could select the columns to display from a list.

Our results table was built from a flexible table model that used reflection and formatters to display the results. The column headers were keyed off the bean property. So all we stored in the search criteria was the ordered list of property names. (depending on how you implemented custom fields may make this a bit more complex, but Jakarta Commons' bean utils allows for indexed properties...)

I hadn't really given much thought to per-user or per-system column displays. I suppose those could provide the default column list for searches, where the hierarchy is JIRA defualts -> system defaults -> user defaults -> specified in search.

Are you saying - for each search, customise which columns are displayed?

If so - that is even more complicated than just customising which columns are displayed on a per-user or per-system basis.

I don't think this issue has really been resolved... perhaps this was mistakenly closed when custom fields were added? This is the ability to customize which fields are shown in a search.