Skip to content

About

Close Context: month-end close room for Jira and Confluence with a Rovo agent (Atlassian Forge, Codegeist 2026). Demo data only.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

6 Commits

Folders and files

Repository files navigation

Close Context

A month-end close room inside Jira and Confluence, with a Rovo agent (Close Controller) that flags what is blocking close, drafts flux commentary from recorded drivers, and files follow-up work items. Built on Atlassian Forge for Codegeist 2026.

All data is synthetic demo data for a fictional company (Larkspur Outdoor Goods, Inc.). There is no connection to real books or any accounting system.

What's in the app

Surface Forge module What it does
Close room jira:projectPage (UI Kit) Progress, ranked blockers, flux table with commentary review/approve, checklist with status changes, "File follow-up" per blocker, buttons that open Rovo chat with the agent
Issue panel jira:issuePanel (UI Kit) Shows whether a work item is blocking close and the live blocker status
Close memo confluence:globalPage (UI Kit) Material swings with commentary; publishes a close memo page into a Confluence space
Close Controller rovo:agent Prompt in resource/agent/prompt.txt; jobs: blockers, flux commentary, follow-ups, owner workload
Actions action (x7) get-close-status, get-flux-review, draft-flux-commentary, save-flux-commentary, create-close-follow-up, get-related-close-work, get-my-close-workload
MCP tools rovo:mcp Exposes six actions to customer-built and third-party agents; see docs/skill.md
Teamwork Graph api.asUser().requestTeamworkGraph atlassianUserAssignedJiraWorkItems curated query for owner workload (Preview API)

Guardrails: agent-written commentary is always saved as an unapproved draft; only a person can approve it in the close room. The agent never invents drivers or amounts (enforced in the prompt and by the deterministic draftCommentary which marks "owner input needed" when no driver exists).

Layout

manifest.yml                 Forge manifest
src/index.js                 UI resolvers + Rovo action handlers
src/lib/close.js             Pure close logic (flux, blockers, summary, drafts, Jira/Confluence payloads)
src/lib/demoData.js          Fictional company dataset (period 2026-10)
src/lib/store.js             Forge KVS persistence
src/lib/atlassian.js         Jira, Confluence and Teamwork Graph calls (asUser)
src/lib/inputs.js            Hardening for LLM-supplied action inputs
src/frontend/*.jsx           UI Kit frontends
resource/agent/prompt.txt    Rovo agent prompt
scripts/seed-jira.mjs        Optional: create the demo checklist as Jira work items on a test site
scripts/offline-lint.cjs     Runs Forge's client-side linters without CLI login
test/*.test.js               Unit + action tests (node:test)
docs/                        Demo script, Devpost draft, skill.md

Install and run

Prerequisites: Node 22+, an Atlassian account, and a Forge API token (https://id.atlassian.com/manage-profile/security/api-tokens).

npm install
npm i -g @forge/cli            # or use npx @forge/cli
forge login                    # or export FORGE_EMAIL / FORGE_API_TOKEN
forge register close-context   # replaces the placeholder app.id in manifest.yml
forge lint
forge deploy -e development
forge install -e development --site <your-site>.atlassian.net --product jira
forge install -e development --site <your-site>.atlassian.net --product confluence

Jira is the required app and Confluence is optional (app.compatibility in the manifest), so both share one installation and one Forge storage. Install Jira first, then Confluence.

A free developer site: forge site provision (or https://go.atlassian.com/cloud-dev). Rovo must be enabled on the site for the agent and chat buttons.

Optional demo seeding (test site only; dry run by default):

JIRA_PROJECT_KEY=CLOSE node scripts/seed-jira.mjs            # prints payloads
JIRA_SITE=... ATLASSIAN_EMAIL=... ATLASSIAN_API_TOKEN=... node scripts/seed-jira.mjs --apply

The close room auto-loads the demo period on first open; "Reset demo data" restores it.

Tests and lint

npm test               # 21 tests: close logic, input hardening, action handlers with Forge APIs mocked
npm run lint:offline   # Forge manifest schema + client-side linters, no login needed
forge lint             # full lint (needs a logged-in Forge CLI)

Scopes

storage:app, read:jira-work, write:jira-work, read:space:confluence, read:page:confluence, write:page:confluence, read:graph:user:atlassian, read:graph:issue:jira.

License

MIT

About

Close Context: month-end close room for Jira and Confluence with a Rovo agent (Atlassian Forge, Codegeist 2026). Demo data only.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages