Can I see all my Jira tickets across multiple projects in one place?

Yes, for your own tickets, and this is better than it used to be. The Your Work page (jira.atlassian.net/jira/your-work) lists every unresolved issue assigned to you across every project you can access, and a saved JQL filter — assignee = currentUser() — returns the same set and can be pinned as a favourite. Neither of those is new; what's new in the 2026 Summer Release is that you can point that same cross-project JQL at the unified List view and get parent/child hierarchy and custom grouping on top of it, not just a flat list.

Does Jira's new List view fix the cross-project rollup problem?

Partly. Per Atlassian's Summer 2026 release notes, the old List and All Work views merged into one List view with 'full parent/child hierarchy' and the ability to 'save custom views,' and it runs on the same JQL that already spans projects — so building assignee = currentUser() into a List view does give you a cross-project list with hierarchy and grouping. The catch is that's a filter you build; the default Your Work page still just buckets by status, and Atlassian's own documentation on the list view and organizing the list don't describe hierarchy or grouping as working any differently across projects than within one — you're leaning on JQL's project-spanning reach, not a purpose-built cross-project rollup.

Can I see my tickets across two different Atlassian sites?

No — and this is the real ceiling, not the projects-within-a-site one. Asked directly whether two Jira Cloud sites could be linked and queried together, an Atlassian product manager answered on the Community forum: 'This isn't possible at the moment.' JQL and the Your Work page are both scoped to the site you're logged into; a second Atlassian instance (a second company, a client's site, an acquired team still on its own tenant) is invisible to both, no matter how you filter or group.

What do people actually build instead?

Workarounds cluster around three moves, all visible across a long run of Atlassian Community threads asking versions of this question: a saved cross-project JQL filter pinned as a favourite, a dashboard 'Assigned to me' or 'Filter Results' gadget built on that same filter, or a Kanban board whose filter includes project in (A, B, C). All three work for tickets you're assigned inside one site. None of them reach a second site, and none of them give you a rollup shaped the way you'd actually group work — by initiative, by client, by whatever column matters to you — rather than by whatever Jira happens to group by.

What's the actual fix for tickets spread across projects and sites?

A layer that sits above Jira instead of inside it. OneView signs in with your real Atlassian account and reads every connected Atlassian site at once — no site picker, no per-site filter to rebuild — then lets you group, roll up, and add your own columns across all of it. That's the piece none of Jira's native views do: Your Work and List view are both bound to a single site's data, however good their JQL and hierarchy get.

All My Jira Tickets Across Projects, In One View

Yes, for your own tickets — the Your Work page and a saved assignee = currentUser() filter both already roll up every project you’re in, and Jira’s 2026 Summer Release List view adds real hierarchy and grouping on top of that same cross-project query. What none of it does is cross a site boundary: if your tickets live on two separate Atlassian instances, nothing native shows them together, and no amount of filtering or grouping fixes that. That’s the honest shape of this — Jira has genuinely gotten better at the projects-within-one-site version of the problem, so the real gap is narrower than most search results assume, and worth naming precisely.

What Jira actually gives you today

Two native surfaces already aggregate your tickets across projects, and both have existed for a while:

Your Work (yoursite.atlassian.net/jira/your-work) — every unresolved issue assigned to you, across every project you can access, grouped by status. It’s automatic; you don’t build anything.
A saved JQL filter — assignee = currentUser() (or assignee = currentUser() AND resolution = Unresolved) returns the same set as a query you can pin as a favourite, add to a dashboard gadget, or use as a board filter, per Atlassian’s own advanced search documentation. Because JQL isn’t scoped to a project, project in (A, B, C) AND assignee = currentUser() is a normal, working query.

Neither of those is new, and neither of them is a secret — they’re the top answer in nearly every Atlassian Community thread asking this question. What’s newer, and less well known, is what you can build on top of them.

The 2026 Summer Release actually changed the ceiling here

Atlassian’s Summer 2026 release notes merged the old List and All Work views into one List view that brings “JQL, AI-powered natural language search, full parent/child hierarchy, and inline editing in one place.” Rolled out fully by the end of August 2026, this means a saved cross-project JQL filter can now be viewed as a List with real parent/child hierarchy and custom grouping — not just a flat table sorted by status. That’s a genuine upgrade, and if your search brought you here expecting “Jira can’t roll up my tickets across projects,” that’s no longer fully true.

It’s also narrower than it sounds. Atlassian’s own documentation on what the list view is and organizing the list describes grouping and hierarchy as list-view features, full stop — neither page describes a rollup mode that behaves differently across many projects than inside one. In practice, getting a hierarchy-and-grouping cross-project view means you build the JQL filter yourself, then view it as a List — the default Your Work page still just buckets by status, with no hierarchy and no custom grouping applied automatically. It works, but it’s DIY, one filter at a time, and every grouping choice is yours to configure and re-configure.

The wall Jira doesn’t move past: two Atlassian sites

Here’s the gap that doesn’t get fixed by List view, JQL, or any filter you build: none of it crosses a site boundary. Asked directly on the Atlassian Community whether two Jira Cloud sites could be linked so issues could be queried together, an Atlassian product manager answered plainly: “This isn’t possible at the moment” (Atlassian Community). A separate, older thread asks the same thing from the assignee angle — “Can I see all issues assigned to me across multiple JIRA instances on one dashboard?” — with the same answer: no.

This matters more than it sounds like it should, because “multiple projects” and “multiple sites” get conflated constantly in search results, but they’re different problems with different ceilings. If your tickets live in two projects on one Atlassian site, JQL and List view solve it. If they live across two sites — your company’s Jira and a client’s, or two companies after an acquisition that never merged tenants — nothing native even sees the second one, no matter how you filter, group, or roll up the first. We go deeper on that specific wall, including why a Marketplace app can’t cross it either, in a Jira report across two sites.

What people actually keep asking for

The forum traffic on this is long-running and largely unresolved by a single native answer, which is itself informative. A representative sample of Atlassian Community threads asking versions of this exact question:

The clearest anchor is “How to create a kanban board that shows all tickets assigned to me across multiple spaces?”, a thread that’s pulled 3,450 views and 7 replies — the answer, as in the others, is “build a JQL board filter with project in (...),” which works for one site and stops there.

The other pattern in these threads: paid Marketplace add-ons show up as the fallback once someone hits the site-boundary wall or wants a rollup shaped their own way. ActivityTimeline’s guide to tracking multiple Jira projects in one board is one of the more detailed examples — a resource-planning layer built specifically because the native cross-project view doesn’t group or roll up the way people actually want to see it.

If your team is spread across projects — or sites

For a single Atlassian site, you now have real options: Your Work for a zero-setup list, a saved JQL filter for anything more specific, and the new List view if you want hierarchy and grouping on top. Build the filter once, save it, and it keeps working.

For everything past that — a rollup shaped by your grouping instead of Jira’s, or tickets that live on more than one Atlassian site — that’s the gap none of the above closes, and it’s what OneView is built for. (Scope isn’t the only axis this breaks on — if what you actually need is a Story Points total, not a ticket list, see summing story points from children to a parent; if what you need is a manager’s dashboard rather than your own ticket list, see a Jira dashboard across multiple projects; if what you need is everyone’s load, not just your own, see Jira capacity planning across projects.) It signs in with your real Atlassian account and reads every connected Atlassian site at once, no site picker, so a cross-project and cross-site view is the same view instead of two logins and two saved filters you maintain separately. You group it, roll it up, and add your own columns — the shape List view’s hierarchy and grouping give you inside one site, extended to however many sites your actual work spans. Start a free trial to see your own tickets rolled up that way.

The same job, on the other tracker

If some of what you’re rolling up isn’t Jira at all — a team still running Microsoft Planner, or a mixed shop with both — the cross-plan version of this exact problem is covered in See all Planner tasks across plans (your tasks: yes, natively; the team’s: no), Planner tasks by assignee across plans (one teammate’s full load, not just yours), a Planner dashboard across all plans, and exporting all Planner plans to Excel when a spreadsheet is the actual deliverable. Jira and Planner hit the same wall for the same reason: neither tool was built to be the rollup layer for work that lives outside it.