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

Removing first 3 columns from Jira list view: checkbox, type and key

Marina Laysha

Why doesn't Jira allow removing the first 3 columns in the list view: checkbox, type and key. They just taking space in front of the columns that I do care to see. In my case, the type is always the same for every row, so it is very useless info that takes precious real state.

Is there any way to hide them?

Accepted answers

Trudy P Claspill

Hello @Marina Laysha

Welcome to the Atlassian community.

It does not appear that those three columns can be hidden or moved. If you hover at the top of other field columns you will see the pointer change to a hand indicating the column can be dragged to another position. And there is a pull-down in the header of the other columns that includes a Hide option. Neither of these is available for the Select, Type, and Key columns.

You might want to ask your admins to contact Atlassian support to find out if there is already a change request opened about this.

All comments

Trudy P Claspill

Hello @Marina Laysha

Welcome to the Atlassian community.

You might want to ask your admins to contact Atlassian support to find out if there is already a change request opened about this.

Dexter de Vera

Hi @Marina Laysha ,

Welcome to the Atlassian community,

Sad to say as of now there is no way to hide the checkbox, type and key in list view.

Dave Rosenlund _Trundl_

That (what Trudy said) said, IMO, @Marina Laysha,I think you'll find over time that those three columns are pretty crucial to the use cases for using List View.

The checkboxes allow you to perform actions on multiple Jira issues at once (bulk editing). That's one of the key features of the List View.
Issue Type is key to understanding which Jira issues are parents and which are children and is useful information in almost any reporting use case.
I might side with you and IssueKey. However, the IssueKey is fundamental to almost every Jira action as it is the only unique identifier of an issue. After a while, you'll likely discover that it's handy to have in a list view. (At least, I did when I was a Structure user -- a similar but more powerful Atlassian Marketplace app.)

I bet Atlassian will resist making any of these 'hideable' (just an opinion).

Best,

-dave

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud