Jira tells you that a ticket changed, then makes you open it and dig through Activity to discover what actually happened.
An inbox should show the comment, status change, or field edit immediately, then take you straight to the exact change. Atlassian should seriously study Linear’s inbox.
I posted Cascade here recently, but the short demo flew past the part I care about most: the Inbox.
My problem with Jira notifications was not just the volume. It was the second step.
A notification tells me something happened. Then I still have to open the ticket, find the activity, look through its history, and work out what was actually different.
I wanted that entire loop to take one click.
Cascade groups new comments, u/mentions, assignments, status moves, and field edits by ticket. For an edit, the Inbox shows a small added and removed excerpt immediately.
Click it and the ticket drawer opens the exact edit, with a word-level diff and “Since your last visit” already applied.
When I’ve dealt with it, I can mark that item, or the entire ticket, as done and it disappears from the Inbox.
https://reddit.com/link/1vskxbi/video/rd04ctb8rbkh1/player
This is part of Cascade for Jira, the Chrome extension I shared here recently. I’m the developer.
For people who live in Jira: would this replace part of your email and notification workflow, or is there an activity type it would still need to catch?
I posted Cascade here recently, but the short demo flew past the part I care about most: the Inbox.
My problem with Jira notifications was not just the volume. It was the second step.
A notification tells me something happened. Then I still have to open the ticket, find the activity, look through its history, and work out what was actually different.
I wanted that entire loop to take one click.
Cascade groups new comments, mentions, assignments, status moves, and field edits by ticket. For an edit, the Inbox shows a small added and removed excerpt immediately.
Click it and the ticket drawer opens the exact edit, with a word-level diff and “Since your last visit” already applied.
When I’ve dealt with it, I can mark that item, or the entire ticket, as done and it disappears from the Inbox.
This is part of Cascade for Jira, the Chrome extension I shared here recently. I’m the developer.
For people who live in Jira: would this replace part of your email and notification workflow, or is there an activity type it would still need to catch?
I've been spending a ridiculous amount of time in Jira, and eventually started getting annoyed by all the little things that make working in it slower than it needs to be.
So I built Cascade for Jira.
Here's a quick 45-second video showing it running on a real Jira project:
https://reddit.com/link/1vld4kg/video/kgpb8s3yxpih1/player
The idea isn't to replace Jira. It's to make the parts you interact with all day a bit better.
And my team loves this.
Some of the things it adds:
It runs locally in the browser using your existing Jira session, so there's no separate account, OAuth setup, backend, or Jira admin approval needed.
The core features are free, and I'm currently giving the more advanced export functionality away during Early Access.
I'm mainly looking for people who use Jira heavily to try it and tell me what I'm missing.
If you spend a few hours a day in Jira, I'd especially be interested in hearing which part of Jira annoys you the most. That's probably where I'll build next.
I've been spending a ridiculous amount of time in Jira, and eventually started getting annoyed by all the little things that make working in it slower than it needs to be.
So I built Cascade for Jira.
Here's a quick 45-second video showing it running on a real Jira project:
https://reddit.com/link/1vld359/video/nfxn08jfxpih1/player
The idea isn't to replace Jira. It's to make the parts you interact with all day a bit better.
AND MY TEAM LOVESS IT.
Some of the things it adds:
It runs locally in the browser using your existing Jira session, so there's no separate account, OAuth setup, backend, or Jira admin approval needed.
The core features are free, and I'm currently giving the more advanced export functionality away during Early Access.
I'm mainly looking for people who use Jira heavily to try it and tell me what I'm missing.
If you spend a few hours a day in Jira, I'd especially be interested in hearing which part of Jira annoys you the most. That's probably where I'll build next.
Edit: I actually ended up building it. I got tired of the workarounds, so I went ahead and coded a Chrome extension to fix it. It renders the hierarchy as a tree inside Jira and lets you export it. Because it runs directly in your own browser tab, you don't need a site admin to install or approve it. I also added a bunch of other features that my colleagues wanted. Not sure if they'll help you.
Search for Cascade for Jira on the Chrome Web Store.
Transparency note: The core tree view and flat exports (the issue I was facing) are 100% free. I am keeping the advanced features (like indented exports) unlocked for free right now during Early Access to get your feedback, but I do plan to charge a small fee for those later. Let me know what you think!
Hey guys, I'm relatively new to Jira. I have a quick question. Is there a place where I can see all tasks assigned to me in a tree format (e.g., Epic -> story -> tasks -> subtasks)? That way, I can see the parent-child thread in one single table.
I'm assigned across a few Jira projects at once, and the daily reality of that is opening three or four boards to answer a question as simple as "what's on me right now." Nothing gives you one consolidated view of your own work. You go project by project, board by board, holding the shape of it in your head.
And I didn't want another drag-and-drop card thing. I don't want to groom a kanban. I want a list, indented, showing what sits under what, that I can read in five seconds and hand to someone.
Then when I actually did need to hand it over, export made it worse. Native export gives you a flat CSV. Epics, stories and subtasks all land in the same column with no indentation, so every time someone outside the team wants a status view, you rebuild the tree by hand in Excel. Every sprint. Again.
Native export gives you a flat CSV. Epics, stories and subtasks all land in the same column with no indentation, so every time someone outside the team wants a status view, you rebuild the tree by hand in Excel. Every sprint. Again.
The Marketplace has apps that fix this. All of them need a site admin to install and approve, which in most companies means a procurement ticket and a three week wait.
So I built Cascade. It's a Chrome extension that renders your issues as a tree table on top of Jira and exports them with the nesting intact.
What it does:
The part I didn't expect to like most: it's just faster. Jira Cloud is heavy, and every board and filter change is a full page load. Cascade fetches once, and everything after that runs locally. I tested it against around 10,000 issues and searching and filtering stayed instant.
It's 95KB, has no server, and sends nothing anywhere. Your data is read from your own session and processed in the browser. No analytics, no tracking, no account.
Free, published a couple of days ago, so it's early and rough in places.
Link: https://chromewebstore.google.com/detail/cascade-for-jira/fjmoolgncjkbnjdecpjpikjeambkihfg
What I actually want to know: is "assigned to me" the right default, or would you need to point it at a whole board or filter for this to be useful?