r/atlassian • u/Big-Barracuda7012 • 9h ago
I’m pausing feature work on my Jira extension. Which problem should it solve best?
I’ve shared a couple of early Cascade demos here before. Since then, I finished this one-minute walkthrough of the current version.
Now I’m deliberately pausing feature work because I may be trying to solve too many Jira annoyances at once.
https://reddit.com/link/1w4fb4q/video/lgxfttf8gxmh1/player
I originally built Cascade for three problems I kept running into:
- Jira notifications told me something changed, but not the exact before and after.
- Hierarchies were difficult to scan, and exporting them produced a flat list.
- Reading and updating issues meant constantly opening more tabs.
The current version combines an Inbox with exact diffs, a tree with slide-out issue details, search and filters, Assigned to me, bulk actions, hierarchy-preserving exports, and keyboard navigation.
For transparency: I’m the developer. Cascade is an independent Chrome extension, not an Atlassian product or Marketplace app. It works through your existing Jira session and permissions and doesn’t require a separate Cascade account.
If you use Jira heavily, which of these is useful enough that you would actually keep an extension installed for it?
- Knowing exactly what changed
- Navigating the hierarchy without opening tabs
- Bulk work and hierarchy-preserving exports
And which feature looks useful in a demo but probably wouldn’t survive your real workflow?
Blunt answers are genuinely more useful to me than “looks good.”