Connect Jira

Generate an Atlassian API token, connect your Jira Cloud workspace, and export Forkpoint tasks as Jira issues.

Connect Jira

Export your Forkpoint tasks as Jira issues. The integration works with Jira Cloud. Your API token is encrypted at rest using AES-256-GCM and is never shown again after saving.

What you need

  • A Jira Cloud workspace you can sign in to.
  • The email address linked to your Atlassian account.
  • An Atlassian API token (created in the next step).

Part 1: Generate an Atlassian API token

  1. Open https://id.atlassian.com/manage-profile/security/api-tokens.
  2. Click Create API token.
  3. Give it a label like Forkpoint so you remember where it is used.
  4. Click Create, then click Copy and save the token somewhere safe.

Atlassian shows the token only once. If you close the dialog without copying it, you will have to create a new one.

Part 2: Add your credentials to Forkpoint

  1. Go to /profile/integrations and click Configure on the Jira card.
  2. Fill in the form:
    • Jira host: your Atlassian Cloud domain, for example acme.atlassian.net. No https://, no trailing slash. Forkpoint strips them automatically if you paste them.
    • Email address: the email on your Atlassian account.
    • API token: paste the token you just copied.
  3. Click Save configuration.

Part 3: Test the connection

Click Test connection. A green toast with your email means Jira accepted the credentials and you are ready to export. A red toast means something is off — see the troubleshooting section below.

Part 4: Set a default project key (optional)

Open the Advanced options section of the form and fill in Default project key (for example MVP). When you export, Forkpoint pre-fills this key so you do not have to pick it each time. Leave it empty to be prompted on every export.

Part 5: Advanced export options

Still inside Advanced options, three checkboxes control what Forkpoint sends to Jira on export:

  • Include time estimate: sends each task’s estimated hours to Jira’s Time Tracking field (Original estimate).
  • Include due date: sends the task’s due date as the Jira issue due date. Useful when your milestones have fixed deadlines.
  • Include story points: maps estimated hours to story points (1 day equals 1 point).

Turn on the ones your Jira project is set up to receive. You can change these at any time.

Troubleshooting

  • 401 Unauthorized: the token was revoked or there is a typo. Generate a new token and paste it again.
  • 403 Forbidden: the Atlassian account is authenticated but does not have permission to create issues in the target project. Ask a Jira admin to grant you the Create issues permission.
  • Host format errors: Forkpoint strips https:// and trailing slashes automatically. If you still see connection errors, double-check the subdomain — it should look like yourcompany.atlassian.net, not the full URL of a board or ticket.

Next

External reference: Atlassian — Manage API tokens.