The problem
Someone goes on leave, and their work goes quiet. The things they own are still due, the things they asked others for are still waiting, the pages they wrote are still the only documentation, and the meetings on their calendar still happen. Teams hand this over with a rushed message on the last afternoon, or not at all. When the person is back, they spend the first day reading notifications to work out what moved.
What Handoff does
- Builds the brief from the Teamwork Graph. Pick the person and the dates. Handoff reads, as you, what the graph knows about them: open work items assigned to them, which of those are due while they are away, the open items they reported that are waiting on someone else, their recent work, open pull requests, the Confluence pages and blog posts they created, the goals and projects they own or contribute to, their calendar events during the leave, and the teams they are in.
- Suggests who should cover. People already on the work (reporters and assignees of those items) and teammates who share projects rank first; a long queue of their own open work counts against.
- Assigns cover in one click. Each covered work item gets a comment that mentions both people, a cover mark that JQL can find (
handoffCover is not EMPTY,handoffAway = "...",handoffUntil < endOfWeek()), and, if you choose, the covering person as assignee. A panel on the work item shows who is away and who covers, only while the mark is there. - Saves the brief as a work item, with every section and link, so it can be shared, watched and attached to the leave request.
- Shows who is away across the site, with days left and who covers.
- Catches people up when they return. Handoff keeps a snapshot of the brief. On return it reads the graph again and shows what changed: items resolved, status changes, reassignments, new work assigned while away, and the new comments from other people, with who wrote the last one.
- The Handoff agent in Rovo does all of this in chat: "I am off next week, what do I need to hand over?", "Who is away?", "Let Priya cover PAY-12 and PAY-15 for Dana", "What changed while I was out?". The same read-only tools are exposed through the Atlassian MCP server for agents outside Atlassian.
Why the Teamwork Graph
The brief needs things Jira alone cannot see: pull requests, pages, goals, calendar events, teams. One graph call per source, as the signed-in person, replaces a dozen product APIs and respects every permission. Cover ranking comes from the same data, so the suggestion is grounded in who already works with the person.
How it is built
Forge only, no egress. The graph adapter uses the typed Teamwork Graph queries (atlassianUserAssignedJiraWorkItems, atlassianUserReportedJiraWorkItems, atlassianUserWorkItems, atlassianUserPullRequests, atlassianUserContent, atlassianUserGoalsAndProjects, atlassianUserLinkedExternalCalendarEvents, atlassianUserInTeams, atlassianTeamMembers, jiraWorkItemComments) with named operations, paging and per-source fallbacks, so a site without a connected calendar still gets the rest of the brief. The brief, the cover ranking, the ADF rendering and the return diff are pure TypeScript with tests. Cover marks are Jira entity properties indexed for JQL; snapshots live in Forge storage.
Built With
- forge
- jira
- mcp
- react
- rovo
- teamwork-graph
- typescript
- ui-kit