Skip to Content
ModulesJira Connector

Jira Connector

Connect your Jira Cloud site so that signing an MSA creates the delivery project, and milestones and status keep themselves in step afterwards without anyone copying anything across.

Who this is for: admins only. Every part of this — the settings tab, the connection, even reading the connection back — is admin-restricted on the server, not merely hidden in the interface.

Before you start

You need:

  • A Jira Cloud site.
  • A classic API token from id.atlassian.com → Security → API tokens. Use the plain Create API token, not the scoped one — the scoped tokens do not work here.
  • An account with permission to create projects and issues, since that is what the connector does on your behalf.

Connecting

Open Settings → Jira. Fill in:

  • Jira site URL — for example https://your-site.atlassian.net. It must be reachable on the public internet (Jira Cloud always is); a Jira server on a private or internal network address cannot be connected.
  • Account email
  • API token
  • Default project template key (optional) — leave it blank to use the Jira default.

Press Connect Jira. All three of site URL, account email and token are required. The token is encrypted at rest and never shown again.

Once connected the panel says which site and account it is connected as, and projects are created when an MSA is signed.

Letting Jira talk back

Creating projects works straight away. Getting status changes made in Jira back into CartonCrew needs one manual step, because Jira has to be told where to send them.

After connecting, the panel shows an Inbound webhook URL. Press Copy — the button says Copied for a moment — then in Jira go to Settings → System → WebHooks and create a system webhook for the jira:issue_updated event pointing at that URL.

That URL is a secret. It carries the shared secret that authenticates the webhook, which is why the panel warns you to keep it private. Treat it like a password: do not paste it into a ticket, a chat channel or a screenshot.

Seeing it on an engagement

Open an engagement. Once it has a Jira project, a Jira card appears showing Project, Epics, Issues and Two-way sync with when it last synced.

The card is read-only — there are no buttons on it. It appears only after a project exists, which happens when the MSA is fully signed, so a brand-new engagement will not show one yet. The project key is a link through to Jira for admins.

Disconnecting

Disconnect Jira asks you to confirm, and tells you what it means: existing links stay, but sync stops. Nothing in Jira is deleted.

If something goes wrong

  • No Jira tab in Settings. The extension is off, or you are not an admin.
  • The panel looks disconnected even though you connected it. You are almost certainly not signed in as an admin — the server refuses to return the connection to anyone else, and the panel shows the empty state rather than an error.
  • Projects are created but Jira changes never come back. The webhook has not been registered in Jira, or was registered for the wrong event. It must be jira:issue_updated.
  • The token is rejected. It is probably a scoped token. Create a classic one.
eSignatureAI Usage & Spend