Community
Products
Jira Product Discovery
Questions
Why was the Key column merged into the Summary column?

Why was the Key column merged into the Summary column?

Someone decided that if we wanted the Key column to be visible in the List view, that you'd merge that column into the Summary field?

Which is terrible for being able to scan the table because "PROJECT-123" is a different width than "PROJECT-4567" and so the user's eye has to jump around as you scan down the Summary column.

It's awful. Please undo that and let us put the Key column wherever we want and not merged into the Summary column text.

It also causes weird user experiences like in this answer: https://community.atlassian.com/forums/Jira-Product-Discovery-questions/How-do-I-sort-by-idea-number/qaq-p/3009980

Where now you have to Sort a column not using its header row? So we now have one special column that gets sorted in a different way? Eesh.

1 answer

1 accepted

1 vote

Answer accepted

Hi Kevin, maybe not our most brilliant moment (based on your feedback) but we did this to have ideas look closer to other items in Jira, after adding support for types (custom types of ideas). Thanks for the feedback - we'll look into it when we iterate on that.