Skip to content
GUIJam
Please leave a star!11 stars

Codegeist 2026 judging guide

GUIJam for Jira is GUIJam's entry in Atlassian Codegeist 2026, category Apps for Software Teams, with the bonus prize Best app with Atlassian MCP. This page walks you through trying it end to end. You need a Jira Cloud site where you're an admin, and Node >=22.12. No AI tool or API key is needed for the main path.

Install the app#

Open the GUIJam for Jira installation link and install the app on your site. Create a Kanban space if you need one and note its key, such as WEB. A new space may need a minute before you can create work in it.

Run the demo app#

git clone https://github.com/francistinao/guijam-jira-demo
cd guijam-jira-demo
pnpm install
pnpm dev

Open the address Vite prints. The GUIJam toolbar is at the bottom right.

Pair GUIJam with Jira#

In Jira, create any ticket, open it, click the GUIJam button under its title, and choose Pair GUIJam. Run the command it shows in the demo folder:

npx guijam jira pair gjp_...

Create the demo tickets#

pnpm seed:jira --project WEB

This creates four tickets with screenshots. Three of them need no AI.

Work a ticket#

  1. In the app, choose Select object and click Subscribe.
  2. Click Link a Jira ticket, then Make the Subscribe button blue and pill-shaped.
  3. Under On apply, move to, pick a status such as In Review.
  4. Set Fill to ocean and Radius to full, then Apply.
  5. About 10 seconds later, open the ticket in Jira. The GUIJam panel shows the before and after screenshots, src/App.tsx with its line, the diff, and the moved status.

The other tickets work the same way: select the heading and type the new text under Content, or select a plan name, which GUIJam finds in src/plans.ts. The badge ticket needs an AI coding CLI and Ask AI.

Try the rest#

  • Undo within 10 seconds of applying, and nothing is posted.
  • Report to Jira from any element, then open the new ticket.
  • Search JQL guijamStatus = applied.
  • With Rovo on and external MCP access allowed, ask an agent "Which UI tickets are waiting for GUIJam?". See Agents and MCP.

How it meets the Forge requirement#

ModuleRole
webtriggerThe bridge that GUIJam on a developer's machine calls, authenticated by a hashed pairing token
jira:issuePanel (UI Kit)Results, status, pairing and device revocation
jira:issueAction (UI Kit)Send to GUIJam
jira:entityPropertyJQL: guijamStatus, guijamFile, guijamAppliedAt
rovo:mcp and two action modulesRead-only MCP tools
Forge KVSPairing hashes, results, idempotency keys and rate limits

The app makes no external calls and no AI calls, and no Atlassian credentials leave Jira. See Security and privacy.

Built during the submission period#

GUIJam's repository began on November 17, 2026, after the submission period opened on October 27, 2026, so all of GUIJam, including this Jira integration, was built during the period. The source is at github.com/francistinao/gui-jam, with the Forge app in integrations/jira-forge.

Limits#

  • Jira Cloud only. Forge doesn't run on Data Center.
  • A developer runs their app's dev server with GUIJam, a dev-only tool.
  • The fourth demo ticket needs an AI coding CLI such as Claude Code.
Documentation