VeloBoardDocs
Docs/Integrations/Jira

Jira integration

Create a Jira issue from any card in two clicks, with all of the project’s required fields pre-populated.

Who can set it up

  • Admins and owners connect the organization to Jira by entering credentials at /admin/jira.
  • Team leaders (and admins/owners) assign specific Jira projects to each team under Teams → Jira Projects.
  • Anyone on the team can then create issues from cards on boards that belong to the team.

Step 1 — connect Jira at the org level

Generate a Jira API token

In Atlassian, create an API token under Account → Security → API tokens. You can use a personal token or a service-account token; the service-account flow is recommended for teams so access doesn’t break if the original admin leaves.

Enter credentials at /admin/jira

Provide the Atlassian site URL (e.g. yourcompany.atlassian.net), email, and API token. VeloBoard encrypts the token server-side with AES-256-GCM before storing it.

Test the connection

The admin page verifies the credentials and lists available projects. Once it succeeds, Jira is connected for the whole organization.

Step 2 — wire projects to teams

Open a team in Teams and go to Jira Projects. Pick which Jira projects the team should have access to. Each team can be connected to multiple projects, and the same project can be shared across teams. Team leaders can customize defaults per issue type — set default fields, hide unsupported fields, require extra fields, or override required flags.

Boards inherit from teams. When you create a board and pick a team, the board gets that team’s Jira projects. Boards that aren’t associated with a team can still see Jira if the current user belongs to a team with projects.

Create a Jira issue from a card

Click the ··· menu on any card and choose Create Jira Issue. A dialog opens with:

  • Project and issue-type pickers (based on what the team has access to).
  • All required fields for that issue type, pulled live from Jira’s createmeta API — including custom fields, story points, components, and more.
  • Card text copied into the summary; you can edit before submitting.

On success, the card shows a Jira chip with the issue key. Click it to open the issue in Atlassian.

What syncs (and what doesn’t)

  • Creation is one-way. VeloBoard creates the Jira issue and stores the issue key and URL on the card.
  • Status sync is not automatic. Moving the Jira issue to Done does not update the card, and archiving the card does not close the issue.
  • Linking existing issues by pasting a URL is not currently supported. Use Create Jira Issue on a new card to get a link.
← Previous
Timer & facilitation