Integrating with Jira Cloud

FireHydrant can create tickets in Jira for each of your incidents, with linked tickets for follow-ups to prioritize after the incident. This way all of the actions proposed during an incident are tracked in your existing project management workflows for estimation and scheduling.

Setting up Jira Cloud integration


A user who is both a Jira Cloud administrator and an Owner in FireHydrant must configure this integration.

Note: FireHydrant recommends using a generic Jira Cloud service account rather than an individual named user to avoid problems if the named employee were to depart the organization.

The Jira Cloud service account used to authorize the integration must have these minimum functional permissions:

  • Project Permissions
    • Browse Projects
  • Issue Permissions
    • Assign Issues
    • Close Issues
    • Create Issues
    • Edit Issues
    • Link Issues
    • Move Issues
    • Schedule Issues

Some of the other things the Service Account should have access to include:

  • Read all Jira ticket types to be used with FireHydrant.
  • Read all Jira fields and custom fields to be mapped in FireHydrant.


Note: Make sure you are currently logged into Jira as the service account and not in your personal account, otherwise the connection will be established with your personal account.

Go to Integrations > Jira Cloud and locate the Jira Cloud integration. You can also view our Jira Marketplace listing, which will also list the same instructions.

Integrations page Jira cloud

Click the '+', and then click Authorize Application. This will take you to Jira where you can authorize FireHydrant's application.

Configuring webhook to FireHydrant

To see updates to your tickets reflected in FireHydrant, add a Webhook to Jira. In FireHydrant, access the Jira Cloud integration settings, and copy the Webhook URL.

Jira webhook URL

In Jira, have your Jira administrator configure a Webhook listener for FireHydrant using the copied URL. Set this webhook for the projects you plan to use with FireHydrant (or all issues), and then check the Issue created and Issue updated boxes.

Jira webhooks

Enabling ticketing attribution w/ account linking

To link the reporter to the person who created a follow-up, FireHydrant needs explicit permission to create tickets in Jira Cloud with the proper reporter.

Note: Each user will need to do this to link their FireHydrant account to their Jira account. Users who do not link Jira in this way can still create action items, but Jira will not show unlinked users as reporters. Instead, Jira shows the user who originally set up the Jira/FireHydrant integration as the user reporting the issue.

To link FireHydrant and Jira accounts, each individual user will need to:

  1. Go to and find the section for OAuth2 Authorizations. User OAuth2 Linking Settings

  2. Click Link in the Jira Cloud row. The next page that opens gives you the option to let FireHydrant to access your Atlassian account. After you click Accept, FireHydrant can correctly associate action items and tickets that you have created with your user ID in Jira Cloud.

Note: Once a user has linked their FireHydrant account to Jira account, creating Follow-Ups linked to Jira projects will set the user as the Reporter. Subsequently, the user will need to have appropriate permissions for the Jira project they're trying to create a ticket in.

Next steps

Now that you've got the Jira integration installed, you can proceed to set up Project Configurations. This will be required before you can make use of other FireHydrant <> Jira capabilities.

For troubleshooting, visit our Troubleshooting Jira Issues article.

Last updated on 2/9/2024