01Connect
Open /settings/providers. The Jira card asks for three fields: the
Base URL of your Jira Cloud site (for example
https://acme.atlassian.net), the email of the Atlassian
account the API token belongs to, and the API token itself, entered
the way a password is. Atlassian issues tokens from
your account's own security
settings; Crewbit has no part in minting one. Press "Connect".
02What comes back
The server encrypts the email and the token together before writing anything, then the Jira card changes shape: its title carries a badge with the base URL you entered, and its description reads "Connected. A Jira source's spec.list and spec.get resolve through it." There is no separate confirmation screen, unlike GitHub's installation hand-off: connecting Jira is one step, not two.
Disconnecting asks first, naming what it costs: "A Run whose specs come from a Jira source stops resolving spec.list and spec.get until this org connects one again." The credential is then deleted outright, not merely marked inactive, so reconnecting means entering the token again from wherever you keep it.
Once connected, "Provider" on a project's "Attach a source" dialog (see creating a project and attaching a repository) offers Jira alongside GitHub, so a Project can read its issues from there instead.
03If this deployment has no encryption key configured
Storing a Jira credential needs a CREWBIT_SECRETS_KEY the deployment sets
up front. Without one, connecting is refused with "this deployment has no
CREWBIT_SECRETS_KEY configured" rather than storing the token unencrypted or failing
with a server error. Crewbit's own hosted deployment has this configured; it only
matters if you are running Crewbit yourself.
04One credential per organisation, unlike GitHub
GitHub's connection is an installation of Crewbit's App, scoped by GitHub's own permission model and revocable from GitHub's side as well as Crewbit's. Jira's is a secret Crewbit holds on your organisation's behalf: encrypted in the database, readable by nobody outside the org that connected it, and gone for good the moment that org disconnects it.