Guides
Practical answers for Jira teams
Each guide answers one question: what Jira can do on its own first, then the workaround, then an app if you want it done for you.
Put the bugs and features with the most revenue behind them at the top of the backlog: what Jira can do on its own, an Automation workaround, and a ready-made app.
Jira's built-in gadgets show lists and charts, not a single KPI. Here is what each native gadget can do, and how to get a big number with a target and a trend for free.
Jira can't post to Discord out of the box. Two ways that work: an Automation rule with a web request (with a copy-paste JSON body), or an app that handles filters, bundling and mentions for you.
Get new bugs, status changes and releases into the right Zoom channel: what still works in 2026, how Zoom's Incoming Webhook fits in, and how to filter and bundle updates.
Size 30 to 100 backlog issues in one refinement: how silent (affinity) estimation works, how to run it with a remote team, and how to get the numbers into Story points.
Scenarios on the Jira story for the product owner, .feature files in the repository for the test runner, and no copying between them: the usual setups and how two-way sync works.