Hi there,
I'm Tanya Maddalena, Product Manager in Jira. We're making it easier to scan and manage your work in Jira's All Work tab by merging multiple fields into one streamlined column.
Until now, the All Work tab displayed individual columns for the hierarchy button, work item key, type, and summary. This could make the list feel cluttered and harder to scan—especially if you manage a high volume of items.
In the All Work tab, you’ll now see a single unified column on the left that combines the hierarchy toggle (for expanding child items), work item key, type, and summary — all in one place.
This column is fixed in position and can’t be moved, so that your key work info stays anchored as you scroll and scan your list.
You can still sort by each individual field! Just click the three dots (…) in the Work item column header and choose which attribute—key, type, or summary—you want to sort by.
And if you're exporting your data, don’t worry: exports remain unchanged. Each field will still appear as its own separate column in CSV or Excel exports, preserving the full detail and structure you're used to.
This isn’t just a visual update—it’s a foundational improvement designed to support future UX upgrades and make Jira faster for you.
By consolidating fields into a single column, we’ve created space for more powerful features down the line while improving page performance today. Faster loading times and a smoother scrolling experience are just the beginning.
To use the merged column in Jira:
Go to your Jira project.
Switch to the All Work tab.
Check out the first column, which now merges hierarchy, key, type, and summary into one neat line.
Cleaner workspace: Reduces visual clutter by eliminating redundant columns.
Faster Jira: Lighter UI means faster load times and better performance.
Future-ready: Sets the stage for upcoming UX improvements that build on this new column structure.
Streamlined navigation: Quickly find the information you need without juggling multiple columns.
Let us know what you think.
Tanya and the Jira team
Tanya Maddalena
6 comments