Connect Jira
Start CoderHelm runs from Jira tickets with the Jira app or a Jira webhook.
You can start runs from Jira tickets. CoderHelm reads the ticket (including screenshots attached to it), picks the repository, and posts its progress and the pull request link back on the ticket.
Open Integrations → Jira. Under How to connect there are two ways.
The Jira app is installed in your Atlassian site. It sends ticket events to CoderHelm, posts comments back, and lets CoderHelm read and create tickets for plans. It can also read Confluence pages and publish release notes there.
- Install the Jira app. Use the link on the Jira page of the dashboard. You need to be a Jira admin.
- Paste your Team ID and secret. The dashboard shows both. In Jira, open the app's Coderhelm Settings admin page and paste them. This links your Jira site to your CoderHelm team.
- Label and assign a ticket. See below.
The app listens for tickets being created, assigned, updated and commented on.
Choose projects
On the same page, switch on the Jira projects CoderHelm should listen to. Tickets in other projects are ignored. If you never change the project list, every project is allowed.
Start a run from Jira
Add the label coderhelm to a ticket and assign it to the CoderHelm user. In practice either one is enough: the label (or any label starting with coderhelm:), or an assignee whose name contains "CoderHelm".
Write the ticket the way you would for a new teammate: what should change, where it shows up, and how to know it works. Screenshots and mockups help; CoderHelm reads them.
A comment on the ticket is handled too. If the run failed, a comment retries it. If the run already opened a pull request, the comment is sent to that pull request as feedback.
A status or field change on its own never starts a run.