Migrating to Jira Multi-Project

Background

In February 2022, FireHydrant added multi project support for its Jira Cloud and Jira Server integrations.  Previously, all incidents and action item related Jira tickets were routed to a single Jira project.  To take full advantage of the Jira multi project feature's flexibility, users will need to modify their existing configuration in the following ways:

  • Configure additional projects in the Jira Cloud or Jira Server integration settings
  • Modify existing runbooks or create new runbooks to use the new ticketing platform-specific incident ticket creation steps

If you have not yet set up Jira integration with FireHydrant, refer to the following documents instead:

Modifying your Jira Integration settings

Note: We do not support required custom Jira fields at this time. If you'd like to use our integration with a Jira project that has required custom fields, you’ll need to remove them.

Access the integration settings for your configured Jira Cloud or Server integration.  Under Projects, for each Jira project you want to be available to FireHydrant users:

  • Configure the settings to map the default Jira ticket type to FireHydrant incidents and actions items
  • Specify the default relationship between linked Jira incident tickets and action item tickets
  • Map FireHydrant action item status to Jira ticket status

Screen_Shot_2022-02-15_at_11.20.26_AM.png

Verifying a project default

Ensure that your organization has a default project configured.  This will act as a fallback in the event that a FireHydrant Jira ticket creation request request cannot communicate with the specified Jira project.  To set a default project go to Organization > Account Overview. From the Account Overview page, choose to Edit the Organization section.  On the Default project for tickets entry select a default project, then click Save organization.

If in the future you disconnect this integration, you will need to reconfigure the default project if you decide to reenable it.

Modifying Runbook Create Incident Ticket steps

Note: The default behavior is to allow only a single top-level incident ticket per FireHydrant incident. There is no limitation on linked action items tickets. If your organization requires multiple top-level incident tickets per incident, please create a support ticket to request that this functionality be enabled for your organization.

As part of Jira multi project support, we introduced new ticketing platform-specific Runbook steps.  This prevents confusion if multiple ticketing platforms are used within an org, potentially resulting in project name conflicts and allows for greater flexibility between ticketing system integrations.

Note: We plan to deprecate the legacy generic Create an Incident Ticket Runbook step at the end of June 2022, and ask all users with existing Jira integrations to please modify their existing Runbooks to use the new Jira-specific steps.

The new Runbook steps are available from the Runbook step menu under Jira Cloud > Create a Jira Cloud Issue or Jira Server (on premise) > Create a Jira Server Issue.

Screen_Shot_2022-02-10_at_1.37.59_PM.png

Accessing multiple projects from action items

Nothing additional needs to be configured to access your newly added Jira projects when users create an action item.  A new Project field will appear when someone creates a Task or Follow up action.  The Jira project selected for an action item can be different from the project in which the incident ticket resides, so you can directly triage actions to different teams contributing to incident remediation.

slackActionCreation.png

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

Contact Our Support Team
Got a Question or Suggestion? We're here to help!
Follow us on Twitter
Get the latest news and updates first