Know when the ticket that matters moves

Issue trackers notify you about everything, which in practice means about nothing: the update that needed you arrives in the same pile as the label someone renamed.

Routing a few tracker events to your phone, and only those, gives the important ones a channel of their own. An urgent bug filed by support or an SLA about to breach is worth an interruption; a typo fix in a description is not.

The events worth turning on

New issue

Most useful for small teams, or filtered to a team or project that files few but urgent ones.

Comment on an issue

Where the question you are blocking usually is.

SLA at risk or breached

The tracker already knows the clock is running out. This makes sure a person does.

Status changed

For the handful of issues you are waiting on, rather than every update in the workspace.

Integrations for this

Each of these sends the events above. Setup is the same for all of them.

Common questions

Will I get a push for every edit?
Only for the events you switch on. Issue updates are noisy, so on Max you can add a payload rule that keeps only status changes or reassignments.
Can I limit it to one team or project?
Yes. Linear webhooks can cover one team, and Jira webhooks take a JQL filter, so only matching issues are sent.