Inspiration
Temporary workarounds often outlive the incident they solved. Their reason sits in one Jira issue, the upstream fix in another, and the decision to remove them in someone's memory. Sunset gives that decision an explicit review trigger and a safe human workflow.
What it does
Sunset records why a workaround exists, which Jira prerequisite should trigger review, the target status, an owner, and a review date. Its project workbench shows live evidence and a review queue. When the prerequisite reaches its target, Sunset says Condition met: review is needed, but removal has not been proven safe. A user can create a Jira retirement task with verification steps, extend the review with a reason, or record retirement. The decision history persists.
Sunset Guide is a Forge Rovo agent with two read-only actions. It explains one decision or lists project review candidates using current Jira status and stored decision records. Inaccessible evidence is reported as unknown.
How it was built
Sunset is an Atlassian Forge app using a Jira project page and issue panel, Forge key-value storage, user-scoped Jira API reads and writes, a rovo:agent module, and reusable Forge actions. Its UI uses React; its backend uses TypeScript. It checks source issue access before showing a record and Edit issues permission before changes. New review tasks use a generic title and body so they do not copy a restricted decision's reason. A claim guard handles uncertain Jira writes without blindly creating duplicate tasks.
Demonstration and limits
On an owned demo Jira site, synthetic issues showed a prerequisite moving to Done and Sunset changing to Condition met. We created and inspected a retirement task, then invoked both Sunset Guide actions. The app passed 12 unit tests, four browser tests, a production build, and Forge lint.
This demonstration uses synthetic issues. We do not claim a customer pilot, measured time savings, Teamwork Graph integration, or a verified external MCP client. Evidence is checked on page load, manual refresh, and Rovo invocation; there is no background monitoring or automatic removal.
Challenges and next steps
Jira permissions shaped the design: reads run as the current user and shared tasks avoid restricted decision details. Next we will test with two Jira users, validate an independent install, and run a real engineer pilot. Engineers keep the final removal decision.
Built With
- atlassian-forge
- jira
- react
- rovo
- typescript