Your team already plans in a tracker. Instead of retyping a ticket into CodeLynq, connect the tracker to a project: a label on a ticket starts the task, and CodeLynq reports back on the ticket.
Connecting a tracker is for organization admins and the project's owner.
How it works
- Someone adds the label (by default
codelynq; in Azure DevOps it is a tag) to a ticket. - CodeLynq creates a task in the connected project from the ticket's title and description, comments that it picked it up, and drafts the spec.
- The spec appears as a comment on the ticket, with the questions the technical lead still has.
- A member of the project answers on the ticket:
/codelynq approveapproves the spec. If the connection allows it, the development run starts straight away, through the same checks as the Run button./codelynq feedbackfollowed by what should change sends that to the spec chat; an updated spec follows on the ticket.
- The pull request link goes to the ticket when it opens, and a last comment says when the task is done or failed.
Only a comment that starts with /codelynq is a command. The commenter's email in the tracker must belong to a member of the CodeLynq project; anyone else gets a reply asking them to use CodeLynq instead.
Connect a tracker
Open the project, go to Settings → Issue trackers and choose Connect a tracker.
Jira (Cloud)
- Jira site URL:
https://..atlassian.net - Email and API token of the Atlassian account CodeLynq should comment as. Create the token at id.atlassian.com under Security → API tokens.
- After connecting, copy the webhook URL (it is shown once). In Jira go to Settings → System → WebHooks → Create a WebHook, paste it, and tick Issue created, Issue updated and Comment created. You can limit it to one project with JQL.
Linear
- API key: Settings → Security & access → Personal API keys.
- After connecting, copy the webhook URL. In Linear go to Settings → API → Webhooks → New webhook, paste it, pick the team, and tick Issues and Comments.
- Paste the webhook's signing secret in CodeLynq as well: CodeLynq then rejects any call Linear did not sign.
Azure DevOps Boards
- Project URL:
https://dev.azure.com/./ - Personal access token with the scope Work Items (Read & write).
- After connecting, copy the webhook URL. In Azure DevOps go to Project settings → Service hooks → Create subscription → Web Hooks, and create three subscriptions with that URL: Work item created, Work item updated and Work item commented on.
When comments stop arriving
If the tracker refuses a comment (an expired token, for example), the connection shows the reason under Settings → Issue trackers, and CodeLynq tries again every couple of minutes. Replace the token and the missed comments follow.
Pause a connection to stop new tickets from starting tasks; tasks that already exist are unaffected. Disconnecting keeps the tasks it created.