Jira

Connect Furl to Atlassian Jira using an API token to read projects and issues, create and comment on issues, and trigger Furl flows when issues change.

Description

The Jira integration lets Furl track and prioritize remediation work alongside the rest of your engineering work. Furl reads accessible projects and issues from Jira, can open new issues and add or edit comments, and can react to webhook events when issues are created or commented on.

Configuration Steps

1. Generate an Atlassian API token

   • Sign in to Atlassian and visit https://id.atlassian.com/manage-profile/security/api-tokens.
   • Click Create API token, give it a meaningful label (e.g., Furl Integration), and copy the token immediately — Atlassian only shows it once.

2. Identify your Atlassian domain

   This is the subdomain in your Jira URL. If your Jira lives at https://acme.atlassian.net, your domain is acme.

3. Confirm the user has the right project access

   Furl uses the API token to act as the user who created it. We recommend creating the token under a dedicated integration account (not a real employee’s account) so the integration doesn’t break if someone leaves. The account needs read access to the projects you want Furl to see, and write access if you want Furl to create issues or comments.

Required Configuration

Provide the following in Furl:

• Token — The Atlassian API token you generated.
• Username — The email address of the account that owns the token.
• Domain — Your Atlassian subdomain (e.g., acme for https://acme.atlassian.net).

Supported Capabilities

Datasources

• Projects → Retrieve accessible projects from Jira.
• Issues → Retrieve issues from Jira. Accepts an optional Project Key input to scope results.

Actions

• Create issue → Create an issue in a Jira project. Inputs: summary, issue type (e.g., Task, Story), project key, optional description.
• Get issue → Retrieve issue details by issue key (summary, description, status, assignee, link).
• Comment on issue → Add a comment to an issue.
• Edit comment on issue → Update an existing comment by ID.

Triggers

Furl can react to Jira events via webhooks. Configure a webhook in Jira pointing to the URL Furl provides for the trigger.

• Issue Created (Webhook) → Fires when a Jira issue is created (jira:issue_created). Outputs the issue key, ID, summary, description, and status.
• Issue Commented (Webhook) → Fires when a comment is added to an issue (comment_created). Outputs the issue key, ID, comment ID and text, and the comment author. Supports an optional Prefix input for filtering by comment text.

Troubleshooting

• If Furl returns 401, the token is invalid or the username doesn’t match the account that owns it.
• If projects or issues are missing, check the token-owner’s permissions in Jira. Atlassian permissions are project-scoped, so an account with read access to one project may not see another.
• For the comment edit action, the API only allows editing comments authored by the same account that created them.
• For webhook triggers: verify the webhook URL in Jira’s webhook settings exactly matches the URL Furl provided. Webhooks are scoped to specific event IDs (jira:issue_created, comment_created).