Jira and Linear
Link Jira and Linear tickets to tasks, and connect their MCP servers so your harness reads tickets on your own login.
EasyCode works beside Jira and Linear in two ways today. A task can carry a link to its ticket. And your harness can read and update tickets itself, through the vendor's MCP server, signed in on your own login.
Org tracker sync is switched off for now
Syncing tickets onto the board for the whole org is built but switched off. Settings → Integrations says Trackers are switched off for now. Ticket links and MCP servers, below, work without it.
Link a ticket to a task
On the board, click New task.
Fill in the Title and Product, then paste the ticket's address into Ticket link, for example
https://northwind.atlassian.net/browse/ENG-123 or https://linear.app/northwind/issue/ENG-123.
Create the task. The task keeps the link and opens it in one click.
EasyCode never fetches or reads the ticket behind a link. It accepts only https links on Jira Cloud
(*.atlassian.net) and Linear (linear.app) with a ticket key such as ENG-123. Anything else gets
Paste a Jira or Linear link. A link is rebuilt from its parts, so any query or fragment in it is dropped.
Let your harness read tickets
To have an agent read a ticket, update it or file a new one, connect the vendor's MCP server to your harness. The harness signs in to Jira or Linear on your own account and keeps its own token; EasyCode never sees it.
In the desktop app, open Settings → Harnesses and scroll to the MCP servers.
Click Connect Linear to all, or Add an MCP and pick Linear or Atlassian (for Jira and Confluence).
Each harness runs its own add command, then its own sign-in. Finish it in the browser page that opens, one at a time. The row then says the server is connected.
When you paste a ticket link into a new task, EasyCode offers the same: Want your harness to read this ticket? links to the right server in harness settings. You can create the task without connecting.
Which harnesses connect in one click?
One click. EasyCode runs claude mcp add and claude mcp login.
Ask your Atlassian admin
If Atlassian refuses the sign-in, your Atlassian organization hasn't allowed the app yet. An Atlassian admin approves it once for the site, then you try again.
Next
Something wrong or missing? Suggest a change