INTEGRATION / BACKLOG
Follow-ups agreed in the incident channel shouldn't die there. Land them in Backlog.
If your engineering org plans its work in Nulab's Backlog, you know the pattern: during an outage someone says “I'll preserve the logs” or “we should roll that config back,” and a week later nobody can find where that was written down. Incident Lake captures response tasks as they come up in the Slack or Teams thread. With an admin's opt-in, it opens them as Backlog issues and keeps status in step on both sides.
1
Capture
Work that comes up mid-incident is confirmed as a task, one at a time
2
Open the issue
If an admin has enabled it, the task becomes a Backlog issue
3
Stay in sync
Status changes flow both ways and stay on the incident record
Illustrative mock. Demo video coming soon.
What it does
- Creates Backlog issues from incident tasks (when an admin enables it)
- Two-way sync of status transitions (when an admin enables it)
- Auto-links Backlog URLs pasted into the thread
What it doesn't do
- Replace Backlog. Day-to-day planning stays where it is.
- Create issues or change status before an admin turns two-way sync on
- Set severity or call an incident resolved. A person decides.
- Page or phone the on-call engineer
Setup at a glance
Connect Backlog
From the integrations area in admin settings, pick Backlog and enter your connection details. Secrets are encrypted per tenant.
Decide on two-way sync
An admin chooses whether issue creation and status transitions sync both ways. Nothing two-way runs until they do.
Try it on a test task
Add a task to a test incident and check the issue and its status on the Backlog side. We'll walk you through the exact steps and timing during onboarding.
FAQ
Could it flood Backlog with issues we didn't ask for?
Issue creation and status sync only run two-way once an admin enables them. Connections to monitoring, code and documentation tools are read-only.
Some of our teams use Jira. Is that covered too?
Yes. Jira gets the same task sync and URL auto-linking. If you run both, we'll help you plan the setup during onboarding.
We're on Microsoft Teams, not Slack. Does it work?
Yes. Tasks are captured the same way in Teams threads as in Slack threads.
Related reading
Connect Backlog and try it free
Start on the free plan. Your Backlog workflow doesn't change; see whether incident follow-ups actually make it into the backlog this time.
Start free (2 min) →