Customizing the List View in the Operations Menu

[Jonas Hellwig]

Hi,
in a project we use the template "bug monitoring". When I switch to the "Tasks" menu here, I get all tasks of the project listed. Unfortunately I can't find the way how to edit columns in this view.

In the list view there are some fields that I don't need: e.g. Created.
However, other fields that are important for us are missing. How can I change the default list view so that it is tailored to the needs of the team?

BR
Jonas 

[Hannes Obweger - JXL for Jira]

Hi @Jonas Hellwig

welcome to the community!

I assume you're referring to the project-level issue view, under a URL like

<something-something>/projects/<project-key>/issues

?

If that's the case, the columns in this view cannot currently be modified. You have to use the "global" Advanced Issue Search to do that; to get there, you can click the "Go to advanced search" button at the top of the screen. 

In the Advanced Issue Search, you can modify the columns via the "Columns" button at the top-right of the list view. You can also save a particular column configuration as a filter. 

Hope this helps,

Best,

Hannes

[Hannes Obweger - JXL for Jira]

... and just to add to the above: If you're open to solutions from the Atlassian Marketplace, my team and I are working on an app that I believe would be a great fit for your use case: JXL for Jira.

JXL is a full-fledged spreadsheet/table view that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It integrates into the project side bar, making it very easy to access to team members, and allows configuring the perfect table view(s) for a given use case. 

This is how it looks in action:

JXL also comes with a number of advanced features, ranging from support for configurable issue hierarchies, to issue grouping, sum-ups, and conditional formatting.

Any questions just let me know,

Best,

Hannes

[Jonas Hellwig]

Hi Hannes,
unfortunately you confirmed my fears. Thank you anyway for the quick response and the good description of a workaround.

Best regards
Jonas