Resurface turns retro & sprint action items into owned, due-dated Jira issues that resurface until they're done. Auto-nudges owners, tracks carry-overs, proves follow-through. Free for up to 10 users. Runs on Atlassian.
The inspiration came from seeing the same pattern over and over again.
Teams would have thoughtful retrospectives, identify great improvements, agree on action items... and then two sprints later we'd be discussing the same problems because those actions had quietly disappeared.
There are plenty of great retrospective tools, but I felt there was a gap around what happens *after* the retro. I wanted to build something that helps teams follow through on the improvements they already committed to, without forcing them to change the retrospective tool they already like using.
Report
How does it handle cases where an action item gets reassigned mid-cycle, does the due date move with the new owner or stick with the original?
Report
Maker
@nurcan6g81 Good question! The due date stays with the action item. Reassigning it doesn't change the timeline automatically, since the expectation is usually that the commitment itself hasn't changed. If needed, you can always update the due date separately.
Report
Would love a Slack recap each Friday that lists what resurfaced, what got closed, and what's been stuck for two cycles. Seeing it in chat without opening Jira would make the follow-through loop feel less invisible to the wider team.
Report
Maker
@parkpiper66988 I like that idea a lot. A weekly digest with what resurfaced, what got completed, and what's been overdue for a while would make it much easier to keep the whole team in the loop without everyone having to open Jira. Thanks for the suggestion, I'm adding it to the backlog.
Report
No reviews yetBe the first to leave a review for Resurface by OutpostLabs
How does it handle cases where an action item gets reassigned mid-cycle, does the due date move with the new owner or stick with the original?
@nurcan6g81 Good question! The due date stays with the action item. Reassigning it doesn't change the timeline automatically, since the expectation is usually that the commitment itself hasn't changed. If needed, you can always update the due date separately.
Would love a Slack recap each Friday that lists what resurfaced, what got closed, and what's been stuck for two cycles. Seeing it in chat without opening Jira would make the follow-through loop feel less invisible to the wider team.
@parkpiper66988 I like that idea a lot. A weekly digest with what resurfaced, what got completed, and what's been overdue for a while would make it much easier to keep the whole team in the loop without everyone having to open Jira. Thanks for the suggestion, I'm adding it to the backlog.