Inspiration
Important launch decisions often depend on work spread across Jira issues and assumptions recorded in Confluence. We wanted teams to see whether their prerequisites still support a decision, and to trace the evidence behind that conclusion.
What it does
CAUSAL is a decision-assurance app for Jira. Teams record a decision, its launch date, and the prerequisites that must be completed first. CAUSAL compares Jira forecasts with confirmed deadlines, checks quoted conditions against Confluence pages, and preserves accepted baselines and analysis evidence.
When a forecast misses a deadline or source evidence changes, CAUSAL flags the decision for review and explains why. It also produces a downloadable evidence record with a SHA-256 hash.
How we built it
We built CAUSAL on Atlassian Forge. It uses a Jira panel, Jira and Confluence evidence checks, and a Teamwork Graph diagnostic that compares graph links with Jira REST links.
Challenges we ran into
Connecting Jira, Confluence, and Teamwork Graph across different sites and permissions required careful testing. We also had to make the results distinguish confirmed rules from forecasts and show uncertainty when evidence is missing or inaccessible.
Accomplishments that we're proud of
We built a working flow that saves a decision baseline, checks Jira prerequisites, verifies a quotation against a Confluence page, flags a missed deadline, and preserves analysis evidence for later review. We tested the workflow on a separate Jira and Confluence site.
What we learned
Decision tools need to show not only a status, but also the rule, source, and facts behind it. Forecasts are not guarantees, so CAUSAL keeps them distinct from confirmed conditions and makes evidence changes visible.
What's next for CAUSAL
Next, we want to make the Rovo experience easier to discover, improve onboarding for new sites, and expand the decision evidence and dependency views.
