The Jira integration with HappyFox Workflows lets you create, update, and link Jira issues — including adding comments and attachments — as an action within your workflow builder.
Note: This is separate from HappyFox Help Desk's native Jira integration, which keeps tickets and Jira issues in two-way sync on an ongoing basis. Use this Workflows integration when you want to create or update a Jira issue as one step within a broader automated workflow — for example, filing a Jira bug when a ticket is tagged a certain way. See the native Jira integration if you want continuous two-way ticket-to-issue sync instead.
Triggers
The Jira integration does not provide triggers. Workflows that include Jira actions are started by a trigger from another connected app — such as HappyFox Help Desk, a webhook, or a smart rule.
Actions
- Create an Issue in Jira
- Update an Issue in Jira
- Update Assignee for an Issue in Jira
- Add Comment
- Add Attachments to an Issue
- Get Issue Details
Use cases
Automatic Jira issue creation: Create a Jira issue automatically when a ticket matches specific conditions, such as a bug report or feature request. See How to Create and Link Jira Issues from HappyFox Workflows for a deep dive.
Bug escalation from support to engineering: When a ticket is categorised as a bug, automatically create a Jira issue in the engineering project with the ticket subject, description, and priority pre-filled — so developers have the context they need without manual handoff.
Support ticket to Jira story: When a customer submits a feature request through HappyFox Help Desk, create a corresponding Jira story in the product backlog, giving the product team visibility into customer-driven demand without trawling through support queues.
Two-way comment sync: When an agent adds a private note to a HappyFox ticket, automatically add a comment to the linked Jira issue — keeping the engineering team updated on customer-reported details without switching between tools.
Jira issue re-assignment on ticket ownership change: When a HappyFox ticket is reassigned to a different agent or team, update the assignee on the linked Jira issue so both systems stay in sync without manual updates.
Attachment forwarding to Jira: When a customer attaches a screenshot or log file to a support ticket, automatically add that attachment to the corresponding Jira issue, so developers have the evidence they need to reproduce and fix the issue.
Enriching workflow steps with Jira issue details: Use the Get Issue Details action to retrieve the current status or priority of a Jira issue mid-workflow, and use that data to conditionally route or update the HappyFox ticket — for example, closing the ticket when the linked Jira issue is marked as resolved.
Assignee routing: Update the Jira issue's assignee based on the ticket's category or team ownership.
Issue status lookup: Retrieve issue details to surface current Jira status information within the ticket.
Your Jira integration can now create, update, and link issues as part of your workflow. Next, see how to create and link Jira issues from HappyFox Workflows for field-level mapping guidance between ticket data and Jira fields.
Plan
- Supported on all HappyFox Workflows plans.
- A Jira Cloud or self-hosted Jira account is required. Enable the Self Hosted? toggle during setup if you are connecting a self-hosted instance.
Permissions
- You must have administrator access to HappyFox Workflows to configure the integration.
- You must have access to the Jira developer console to create the OAuth app and retrieve credentials.
Setting up the integration
- Login to your HappyFox Workflows account.
- Under the Apps section, go to the Jira section.
- Copy the callback URL displayed on this page.
- Now, log in to your Jira account
- Then switch to the Jira developer console by opening this link.
- Click on Resources-> Developer console
- Then, click Create->OAuth 2.0 Integration
- Name your app
- Enable the permissions under the permission tab for -Jira platform REST API, User identity API
- Now click on the Configure button next to Jira platform REST API, User identity API and add all their respective scope items.
In addition to the above, please ensure the following scope is also included
- Under the authorization tab, enter the callback URL copied from Happyfox Workflows- Jira app section
- Then, click on the Settings tab to copy the credentials of the new app
- Now enter the Client ID and Secret code copied from the new app in Happyfox Workflows- Jira app section
- Click Save
- The connection between your Jira and Workflows account will now be established and you will be able to see a message for successful integration.
Frequently asked questions
I saved the credentials but no Jira projects appear when I configure the Create an Issue action. Why? This usually means the required scopes were not enabled during Step 1. Return to the Jira developer console, confirm all scope items are enabled under both Jira platform REST API and User identity API, then return to Apps > Jira in HappyFox Workflows, click Reset, and repeat Step 2.
Can I update an issue that was created by a previous workflow action in the same run? Yes. Use the Get Issue Details action first to retrieve the issue key, then pass that value into the Update an Issue action using a merge field. This lets you chain issue creation and update within a single workflow.
Can I create issues in multiple Jira projects from a single workflow? Yes. Each Create an Issue action can target a different Jira project. Add multiple Create an Issue actions to the same workflow and configure each with the relevant project and issue type.
Your Jira integration is now active and Jira actions are available in the workflow builder. Next, build a workflow that creates a Jira issue when a HappyFox Help Desk ticket matches your escalation conditions.
Actions
Each action below lists the fields you configure, along with whether each field is required.
Validation note legend
| Term | Meaning |
|---|---|
| Required | The field must be filled in for the action to run. |
| Optional | The field can be left blank; the action will still run. |
| Text | A plain text entry (single line or paragraph). |
| List (multiple entries) | A repeating group where you can add one or more rows. |
| File | A file attachment reference (URL + filename). |
Create an Issue in Jira
Creates a brand-new issue in a Jira project. You choose the project and issue type, then supply any additional fields — summary, description, priority, assignee, labels, and so on — as key/value pairs. The integration resolves names to IDs before calling Jira.
| Field | Description | Validation |
|---|---|---|
| Project | The name of the Jira project to create the issue in. Must match the project name exactly as it appears in Jira. | Required · Text |
| Issue Type | The type of issue to create (for example, Bug, Story, Task, Sub-task). Must be an issue type that exists in the selected project. | Required · Text |
| Extra Fields | Additional fields to set on the new issue. Each row has a Key (the Jira field identifier — for example, summary, description, priority, assignee, reporter, parent, labels, components, versions, fixVersions, or a custom field key) and a Value, interpreted according to the field type (see the Extra Fields Value Reference below). |
Required · List (multiple entries) |
Update an Issue in Jira
Updates one or more fields on an existing Jira issue. You identify the issue, confirm its project and type — needed to look up field schemas — then supply the fields to change. Uses the same name-to-ID resolution as Create an Issue.
| Field | Description | Validation |
|---|---|---|
| Issue ID | The Jira issue key or numeric ID of the issue to update (for example, PROJ-123 or 10001). |
Required · Text |
| Project | The name of the Jira project the issue belongs to. Used to look up assignable users, components, versions, and field metadata. | Required · Text |
| Issue Type | The issue type name of the issue. Used to identify the correct field schemas for the update. | Required · Text |
| Extra Fields | The fields to change. Each row has a Key (same field identifiers as Create an Issue) and a Value (interpreted using the same type-resolution rules). | Required · List (multiple entries) |
Update Assignee for an Issue in Jira
Reassigns an existing Jira issue to a different user without touching any other fields. The integration looks up the user's account ID from the project's assignable user list before sending the update.
Note: This action's display name in the workflow builder contains a typo — it appears as "Update Assigne for an Issue in Jira" (missing the second "e"). This matches the current product behavior; it isn't a documentation error.
| Field | Description | Validation |
|---|---|---|
| Issue ID | The Jira issue key or numeric ID of the issue to reassign (for example, PROJ-123). |
Required · Text |
| Project | The name of the Jira project the issue belongs to. Used to look up the list of users that can be assigned to issues in this project. | Required · Text |
| Issue Type | The issue type name. Required for field schema lookup during the update call. | Required · Text |
| Assignee | The display name of the user to assign the issue to. The integration searches the project's assignable user list for a matching name and resolves it to the Jira account ID. | Required · Text |
Add Comment
Posts a new comment on an existing Jira issue. The comment is sent exactly as entered — no formatting conversion is applied.
| Field | Description | Validation |
|---|---|---|
| Issue ID | The Jira issue key or numeric ID of the issue to comment on (for example, PROJ-123). |
Required · Text |
| Comment | The text of the comment to add. | Required · Text |
Add Attachments to an Issue
Uploads one or more files as attachments to an existing Jira issue. The integration downloads each file from its source URL and posts it to Jira using the multipart upload API — this works for both Jira Cloud and self-hosted (Data Center/Server) instances.
| Field | Description | Validation |
|---|---|---|
| Issue ID | The Jira issue key or numeric ID of the issue to attach files to (for example, PROJ-123). |
Required · Text |
| Attachments | One or more file references to upload. Each entry must include a download URL and a filename. | Required · List (multiple entries) |
Get Issue Details
Fetches the details of a Jira issue by its key or ID and returns a cleaned-up snapshot — including the issue's ID, key, type, project, status, priority, watch count, creator, reporter, and any attachments. Internal Jira URLs and avatar images are stripped to keep the output compact and usable in later workflow steps.
| Field | Description | Validation |
|---|---|---|
| Issue ID | The Jira issue key or numeric ID to look up (for example, PROJ-123 or 10001). |
Required · Text |
Extra Fields Value Reference
Create an Issue and Update an Issue both use the same Extra Fields Key / Value structure. How a value is interpreted depends on which key you're setting:
| Key | How the value is interpreted |
|---|---|
assignee |
Enter the user's display name; the integration looks up their account ID from the project's assignable user list. |
reporter |
Enter the user's display name; the integration searches Jira users to resolve the account ID. |
priority |
Enter the priority name (for example, High, Medium, Low); resolved to the Jira priority ID. |
parent |
Enter the parent issue key (for example, PROJ-10); sent directly to Jira. |
components |
Enter one or more component names separated by commas; each name is resolved to a component ID. |
versions / fixVersions |
Enter one or more version names separated by commas; each name is resolved to a version ID. |
labels |
Enter one or more label strings separated by commas; split into an array before sending. |
| Custom option fields | Enter the option name; matched against the field's allowed values. |
| Custom user fields | Enter the user's display name; resolved to an account ID. |
| Custom array fields | Enter option names or user display names separated by commas. |
| Custom number fields | Enter a numeric value. |
| Custom date/time fields | Enter a date or datetime string; parsed automatically. |
| All other fields | Sent as plain text. |
Note: For a walked-through example of using Create an Issue with real HappyFox ticket data, see how to create and link Jira issues from HappyFox Workflows.