How do I remove Issue Key from Issue List? Edited

I've installed a trial version of JIRA to test it out. One thing that I've noticed is the Issue Key feature. It seems pointless and it shows on every single Issue in the list, taking up lots of vertical space.

I can't really find a way to remove it though. How do I do this?

2 answers

1 accepted

0 votes
Accepted answer

Hi Andy - Which list are you referring to?

The list on the 'Issue Navigator' page? (from the top-menu banner, select Issues > Search for issues to get there).

If it is that, you can change the columns which show there.

If not, give some more details here and I'm sure someone in the community will be able to help.

The issue list I'm talking about is under the Projects tab on the top bar, when I click on a project. I see a list of Open Issues, with a preview pane beside it.

Each issue is two lines. The first is the key, and the second is the name/description.

Ah. This one?


You can't change the bit I've boxed in red without coding, as far as I know.

It's fixed, because (as Nic mentions) the issue key is really quite fundamental to how JIRA issues are managed and organised.

You can switch your view to 'List View' if you want and hide columns (including issue key).

Yes, but mine looks different. On the right side of your screenshot, I don't have the tabs, or that button.

Anyway, that's odd that you wouldn't be able to remove it. Most people I know swear by JIRA, but so far in my testing, it's a lot harder to use than Celoxis. Ah well. I appreciate the answer.

Ah. Like this one?


If that's what you see, you'd need to click the 'View all issues and filters' link at top right to get to the page I showed in my first screen shot.

I generally set-up more user-friendly keys for projects than your example of 'RIBU1C', because people really do end up talking about issues using the keys.

Check out the projects in Atlassian's own public issue tracker to see some examples of what they do.

Well in our case, each project is going to be a new product that is coming out. The project name isn't under my control.

Your link returned a 502 bad gateway error, btw.

The key doesn't have to be the same as the project name, if that helps.

On the bad gateway error: try again now or a bit later. currently seems have an issue with degraded service

0 votes

The issue key is pretty important, it's the unique identifier for an issue, so I'm not sure why you'd say it's "pointless"?  You'll find people who have used JIRA for more than a few days start talking in terms of the issue key quite a lot because it's short and clear.

But, yes, you're right, sometimes you don't need it at all.  That leads me to the question of which "issue list" you want to remove it from?  I think of the "issue navigator" when you say "issue list" (which you can drop it from), but the key there takes up horizontal space, so I believe you are talking about some other view of issues in a list?

Say I have a project called "RIBU1C". No one is going to refer to tasks as "RIBU1C-3", and "RIBU1C-5". People don't talk like that. "Hey Bob, did you get RIBU1C-3 done for RIBU1C?" No. They'd say "Hey, did you finish developing the housing specs for the RIBU1C, Bob?"

The issue list I'm talking about is under the Projects tab on the top bar, when I click on a project. I see a list of Open Issues, with a preview pane beside it.

Generally, you will find people will talk like that.  If anything, you'll find them dropping an unpronouncable key in favour of something a bit more friendly, but sticking with the numbers because they're the unique identifier.  I would expect to hear people in your office saying "hey, did you fix ribbuk-see-4?"

The issue list you are referring to is a built-in report of a list of issues.  I can see why you'd say the issue key is taking up space, but you'll find your users want to have the key there, both to click on for the full issue view, and so they can yell "hey, did you fix ribbuk-see-4" across the office.


Maybe software developers are different than electrical engineers, I don't know. In my experience, that's not the case. Regardless, that, along with not having native integrated Gantt charts, are the reasons that JIRA has been ruled out for us.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

914 views 3 9
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you