1. Create your organisation
Register an account, then create an organisation from the dashboard. Every organisation is fully isolated — its own members, connectors, ticket fixes, and audit log. Nothing crosses between them.
2. Connect your tools
Go to Connectors and add Jira (the trigger, and where the result is commented back), then one of GitHub or GitLab (where the fix reads code from and opens its draft PR). Confluence is optional — it adds runbook context if you have one.
Use Test connection on each one before wiring up the webhook. A connector that has never been tested will simply contribute nothing when a ticket arrives, and you would rather find that out now than mid-fix.
3. Wire up the Jira webhook
Your Jira connector's card shows a webhook URL, scoped by an unguessable id in the path — Jira Cloud's own webhook configuration has no way to attach a custom header, so that unguessable id is the entire boundary. Point Jira at it for Issue created and Issue updated events.
- Copy the webhook URL from your Jira connector
- In Jira: Settings → System → WebHooks → Create a WebHook
- Paste the URL, and select Issue created + Issue updated
- Set (or confirm) the trigger label on the connector — the default is ai-fix
4. Label a ticket
Add the trigger label to any Jira ticket in the connected project. Noviqent DevOps re-fetches the ticket through your own Jira credentials, checks the real current labels, and — if it carries the label — starts gathering context. Open it from the Ticket fixes list to watch it move through gathering context, reasoning, and (if a fix was possible) a draft PR and its CI result.