Hi Atlassian Community! đź‘‹
We’re happy to introduce Table View in Planyway for Jira—a new way to see, organize, and quickly update work across multiple Jira projects from one structured view.
➡️ Watch a quick demo
đź”— Try Planyway on the Atlassian Marketplace
We’ve received a lot of feedback from Jira users who still turn to Excel when they need to review large amounts of work, compare issues across projects, or make several quick updates.

Spreadsheets can provide a convenient overview, but exporting Jira data also creates disconnected files that quickly become outdated.
With Table View, our goal is to bring that familiar clarity and speed directly into Jira—without requiring teams to export their work or maintain a separate spreadsheet.
Instead of browsing a flat list of issues, you can use Table View to see the relationships between your work items.
Depending on your workflow, you can display:
Epic → Task → Subtask
Task → Subtask
Subtasks only
This makes it easier to understand the full scope of an initiative, follow progress, and navigate between related work items.
Table View can display work items from several Jira spaces together.
This is especially useful for teams managing company-wide initiatives, product portfolios, or programs where epics and tasks are distributed across different projects.
Table View is not only for reviewing your work—you can also use it to make quick updates.
By default, work items at the same hierarchy level follow their Jira rank. You can change their order using drag and drop, and the updated ranking is synchronized with Jira.
You can also sort the table by space when you want to review work project by project. Additionally, you can choose whether to hide completed work or display items completed within a selected period of up to 12 months.
Table View is now available in Planyway for Jira.
đź“– Learn more and see how it works:
https://help.planyway.com/en/articles/15701294-table-view
We’d love to hear how you currently use spreadsheets alongside Jira—and whether Table View could help bring more of that workflow back into Jira.
Mary from Planyway
0 comments