GUIJam for Jira
GUIJam for Jira connects your running app to your team's tickets. A ticket's text and screenshots become your prompt, and whatever you apply, whether a direct edit or an AI variant, is posted back to the ticket once Undo is no longer offered. PMs, QA and designers see the result in Jira without running GUIJam.
- Tickets in. Link a ticket to an element in the Select or Draw panel. Its summary, description and up to four images fill your prompt.
- Results out. Before and after screenshots, the element's
file:line, the diff, who applied it and how, and optionally a status move such as In Review. - Report to Jira. Anyone running the app can file a ticket from an element, with its screenshot and source location already in it.
- For the team in Jira. A GUIJam panel on every ticket, a Send to GUIJam action, and JQL such as
guijamStatus = queued.
How the pieces fit#
GUIJam runs on the developer's machine while they work on their app. The GUIJam for Jira app runs inside Jira Cloud. They talk over one HTTPS connection, set up once by pairing.
Developer's machine
Your app in the browser
GUIJam toolbar and panels
Link a Jira ticket
Report to Jira
Dev server
Vite, Next.js, Nuxt, Astro…
with the guijam plugin
gjd daemon
The only writer to your files
Holds posts for the undo window
Keeps the pairing token
Your AI coding CLI
Only for AI requests
Direct edits need none
Jira Cloud
GUIJam for Jira app
GUIJam panel on tickets
Send to GUIJam action
JQL: guijamStatus
MCP tools for agents
No AI runs in Jira
Your team
Sees before/after, file:line
and the diff without GUIJam
The whole flow#
- Jira admin
1. Installs GUIJam for Jira
- PM, QA, designer
2. Creates a project and UI tickets
- Developer
3. Runs guijam init and pairs
- Developer
4. Links a ticket to an element
- GUIJam
5. Fills the prompt with the ticket text and images
- Developer
6. Edits directly or asks AI, then applies
- GUIJam
7. Writes the file and waits 10 seconds
- Jira
8. Gets before/after, file:line, the diff and the status
- PM, QA, designer
9. Reviews it in the GUIJam panel
A ticket's GUIJam status#
- Not linked
- Send to GUIJamSent to GUIJam
- a developer links itIn progress
- the change is postedApplied
- undone after postingReverted
A developer can also link a ticket that was never sent to GUIJam.
The 10-second undo window#
The daemon holds the post, so closing or reloading the tab doesn't lose it. Undo later and the ticket is marked Reverted.
Who does what#
| Role | What they do | Where |
|---|---|---|
| Jira admin | Installs GUIJam for Jira once per site and approves its permissions. | Jira |
| PM, QA, designer | Writes UI tickets with screenshots, sends them to GUIJam, reviews results in the ticket's GUIJam panel. QA and designers running the app can also report to Jira from any element. | Jira, and optionally the running app |
| Developer | Installs GUIJam in the project, pairs it with Jira once, links tickets to elements, and applies changes by editing directly or asking their AI CLI. | Their app and a terminal |
What you need#
- A Jira Cloud site where someone is an admin, to install GUIJam for Jira once. A free developer site works: go.atlassian.com/cloud-dev.
- Node
^20.19.0or>=22.12.0, and a supported framework. - An AI coding CLI, only for AI requests. Direct edits of text, color and corner radius need no AI at all.
Next: Set up GUIJam for Jira.