Inspiration
Every team makes the same decision twice: once in a meeting, and again months later when nobody remembers it was settled. The decision exists somewhere in a Jira comment, but nothing brings it back when the next related ticket shows up. That's how a billing service ends up half on Postgres and half on Mongo.
What it does
Decision Trail turns Jira into the team's decision log, with no new habits needed.
- Zero-effort capture: any comment starting with
DECISION:,Decided:orAgreed:is captured automatically by a Forge trigger, with author, issue and date. - Issue panel: every issue shows its own decisions and an "Already decided elsewhere" list of related decisions from other issues, so context finds you.
- Conflict warnings: if a new decision adopts something an earlier decision ruled out (e.g. "Use Mongo for the refund ledger" vs "Use Postgres, not Mongo"), the panel flags it before anyone builds.
- Lifecycle: decisions can be marked superseded, and are cleaned up automatically when their issue is deleted.
- Rovo agent "Decision Keeper": ask "What did we decide about the billing database?" and it answers from the same log, citing issue, person and date. It can also log new decisions.
## How we built it
100% Forge, Runs on Atlassian (eligibility confirmed with
forge eligibilityon production): jira:issuePanelbuilt with UI Kittriggeronavi:jira:commented:issue(capture) andavi:jira:deleted:issue(cleanup)rovo:agentwith twoactionmodules:find-decisionsandlog-decision- Forge KVS for storage, so no data leaves Atlassian and there are no external egress domains
- Keyword relevance ranking plus negation-aware conflict detection, covered by unit tests; CI on GitHub Actions runs tests, lint, deploy and install.
Challenges we ran into
Making conflict detection useful without an external LLM. A naive "contains a negation" check flagged agreeing decisions, so we track which terms each decision explicitly rules out ("not Mongo", "no custom auth") and only warn when another decision adopts one of those terms on the same topic.
Accomplishments that we're proud of
A working, non-trivial Forge app that needs zero setup: install it, write a DECISION: comment, and the knowledge starts flowing to related issues.
What we learned
Forge's trigger + KVS + Rovo action combo makes it easy to build one knowledge source and expose it to humans (panel) and agents (Rovo) at the same time.
What's next for Decision Trail
Confluence macro for decision registers, Teamwork Graph integration so decisions link to PRs and pages, and a Marketplace listing.
Try it (for judges)
- Install on a Jira site using the installation link provided in this submission.
- Open any issue, open "Decision Trail" from the issue's Apps (puzzle) button.
- Add a comment starting with
DECISION: Use Postgres for the billing database, not Mongo.Then open another issue about billing and see it under "Already decided elsewhere". - In that second issue, log "Use Mongo for the billing refund database" in the panel and see the conflict warning.
- On a Rovo-enabled site, chat with the "Decision Keeper" agent.
Built With
- forge
- github-actions
- javascript
- jira
- node.js
- rovo
- ui-kit