Jira both ways: sync assignees and jump to the issue faster

If you work with Jira, you don't want to keep two lists of who owns what. Spedy now syncs the assignee in both directions — through a clear per-board user mapping. On top of that, two small shortcuts for everyday work: a clickable Jira icon right on the ticket, and a direct link to connect a repository from an empty Code tab.

Sync assignees between Jira and Spedy

Until now, Jira live sync moved status and comments in both directions — but not the assignee reliably. That changes with the user mapping.

Open the sync configuration under Settings → Integrations → Jira → Sync and pick the board. In the new User mapping section, connect each Jira user to a Spedy user. From then on:

• Jira → Spedy: On import and on every update, Spedy applies the mapped assignee.
• Spedy → Jira: When you reassign a ticket in Spedy, the assignee is set in Jira.

So you don't have to connect every row by hand, use Apply email matches: Spedy suggests matching pairs based on matching email addresses and fills them in with one click. Review the suggestions and adjust individual mappings where needed.

What to know about the mapping

• Only mapped users sync. An unmapped Jira assignee leaves the Spedy ticket unassigned.
• Unmapped Spedy assignees are not pushed to Jira — so no one is removed in Jira by accident.
• The mapping is 1:1 and applies per board, so you can reflect different teams on different boards.

Clickable Jira icon on the ticket

On a ticket synced with Jira, only a permission-gated status badge used to hint that a connection existed — for most roles, there was no way to jump to the issue.

Now a Jira icon shows up in the ticket header. Clicking it opens the matching Jira issue in a new tab. The link is visible to every role that can view the ticket — no extra integrations permission required. You get from the ticket into Jira without hunting for the issue key.

Link a repository straight from the Code tab

An empty Code tab wasn't much help when there simply wasn't a repository connected to the project yet. Now the empty state explains why and offers a way out.

If no repository is linked to the project, the Code tab now reads: "No repository is linked to this project yet." Below it, the Link repository button takes you straight to the board's integration settings, where you add a repository. The button appears if you can configure integrations or edit the board — everyone else keeps the plain hint.

Links in the editor stay their own element

A small but noticeable change when writing comments and descriptions: a link is now its own element. Type right after an inserted link and the new text is no longer pulled into the link. URLs are still auto-linked — the link just doesn't "stick" to the text that follows.

In short

• Jira assignees now sync both ways — via User mapping under Settings → Integrations → Jira → Sync, including Apply email matches.
• Only mapped users sync; unmapped ones are left untouched.
• A clickable Jira icon in the ticket header opens the issue directly in Jira.
• An empty Code tab now offers a direct link to connect a repository.
• Links in the editor no longer pull following text into the link.