FireHydrant can create tickets in Jira for each of your incidents with linked tickets for actions performed during the incident and follow-ups for later. This means that all of the proposed actions during your incident will be tracked in your existing project management workflows along with enabling project managers to estimate and schedule follow-up work.
Our integration is simple to set up: authorize our OAuth2 application if you're using Jira Cloud, choose the types of tickets to create and set your target project.
FireHydrant is an OAuth2 application in the Atlassian Marketplace.
- A FireHydrant organization admin needs to add our Jira Cloud integration and authorize it in Jira Cloud. This requires that the authorizer is a Jira Cloud administrator as well.
- Configure the default issue type for incidents, tasks (actions during incidents) and follow-ups (work to performed after the incident is resolved.)
- Set the type of relationship to use when linking action items to incident tickets. ie follow-ups can 'block' incidents ensuring that all follow-ups are completed before an incident ticket can be completed.
- Add the webhook to Jira if you want to see updates to your tickets reflected in FireHydrant. The webhook target URL is available at the top of the connection configuration page, it can also be found under system, webhooks in your Jira setup pages.
This step is optional
Webhook configuration can be found by clicking Jira Settings in the left-hand navigation bar, System then WebHooks. A direct link to the configuration page can also be found on the connection in FireHydrant.
FireHydrant will create tickets in a single project, that can be specified right within the JIRA configuration settings.
You're now ready to create tickets & action items in FireHydrant and sync them to Jira.
Note: we do not support required custom fields at this time. If you'd like to experiment with our integration, create a new project without the required custom fields. Please reach out to us using the speech bubble at the bottom right corner of the page to share your use-cases of required fields.