Your team mentions blockers in Slack. Jira tickets write themselves.
Standup reminders that go out automatically. PR review requests that escalate when ignored. Sprint digests that write themselves on Friday. This+that handles the operational layer of your sprint so your engineers ship instead of managing process.
Engineering sprints run on communication. That communication is fragmented.
Blockers mentioned, never tracked
An engineer drops a blocker in Slack at 3pm. The scrum master sees it at 4:30pm. It surfaces at standup the next morning. A day is lost.
PR reviews that nobody pings for
A pull request is opened on Tuesday. No one reviews it. It sits. The engineer follows up on Thursday. The sprint slips by two days because of a polite reluctance to nag.
Sprint digests that take an hour to write
Every Friday, someone manually assembles what shipped, what didn't, and what's carrying over. The information exists in Jira, Slack, and email. Pulling it together is manual work.
Standup coordination overhead
Pinging the team for standup. Collecting async updates. Following up with whoever didn't post. This is overhead that happens every single day.
Blockers tracked, PRs nudged, sprint digests written — automatically
Blockers become Jira tickets instantly
When someone mentions a blocker in Slack, this+that creates a Jira ticket with the context, assigns it, and notifies the right person — without a manual step.
PR review reminders that escalate
When a PR has been open for longer than your configured threshold, reviewers get a Slack ping. After another threshold, it escalates to the team lead.
Friday sprint digest, automated
This+that pulls completed tasks, open items, and carry-overs from Jira and email threads — and writes the sprint digest so you don't have to.
Standup reminders without the overhead
Automated standup prompts go out at the configured time. Async updates are collected and summarized. The scrum master sees a digest, not a thread to parse.
Engineering sprint workflows you can set up in plain English
These are the kinds of workflows you can describe to this+that and have running in minutes.
Jira manages tickets. Slack moves messages. This+that connects them.
The gap between where work gets mentioned (Slack) and where work gets tracked (Jira) is where blockers get lost. This+that lives in that gap — watching the conversations, creating the tickets, sending the reminders, and writing the digests. Your engineers don't have to context-switch between tools to manage process. The process manages itself.
See what's slipping through in your engineering inbox. Right now.
Connect your inbox and see how this+that would automate your sprint management — in under 2 minutes.