How it works
From In Progress to In Review, without the clipboard.
You connect the three accounts once and pin a repository. After that, the board is the button.
-
1
Create a workspace
Register with your name, email, and a password. The account opens on a 14-day Solo trial. Nothing is armed yet.
-
2
Verify GitHub, then pick the repo and branch
Paste a personal access token. DeveloperAI calls GitHub as you and lists repositories you can see. Choose the repo, the branch new ticket branches are cut from, and the branch pull requests should land on. That pair is the only codebase Jira is allowed to touch.
-
3
Verify Jira and Cursor
Jira needs the site URL, account email, and an API token. We call
/rest/api/3/myselfbefore saving. Cursor needs an API key, checked against the Cursor API. Each secret is encrypted before it hits MySQL. A failed check does not replace a key that was already working. -
4
Point Jira at your webhook
When every piece is present and the trial or plan is current, the workspace shows a private webhook URL and secret. In Jira, create a webhook for issue updates. Events that are not a transition into your start status are acknowledged and ignored.
-
5
A ticket moves to In Progress
DeveloperAI loads the issue, makes sure your pull-request branch exists, clones the source branch, creates
PROJ-123, writes a small ticket context file, and pushes. Then it launches a Cursor cloud agent on that branch with the ticket as the prompt. -
6
The agent finishes
Cursor calls back when the agent is finished or errors. On success, the ticket branch is merged into your target branch and deleted, Jira gets a comment with the summary and commit link, and the issue transitions to In Review. The temporary workspace is deleted either way.
Still locked until the checklist is green.
A missing token, a missing branch, an ended trial, or a used-up run cap all produce the same kind of answer: the event is refused, and the ticket is left alone.