A Jira connection is required in order for Jira tickets to be created and linked to a monitoring error(s). See our setup guides for instructions on how to connect to your Jira account:
Creating a new support ticket for a monitoring error
From the main error monitoring results page expand a Flow or Apex category which is used to group errors. For example, within each Flow is a breakdown of the errors by Flow element and problem type. Click on the specific error you want to inspect further.
The full error details (see below) are provided containing key information of Flow or Apex errors for the purposes of debugging.
Located on the right hand-side is a panel containing several options, one of which enables the creation of a new Jira ticket for the error.
Creating a Jira ticket
Click on
Add Jira ticket.From the modal, choose the
Jira projectthe ticket will be created under.Add a
summary linefor the ticket (required). By default Gearset pre-populates the subject line with the Flow name and error type.Add a description for the issue. By default Gearset pre-populates the description with information such as Flow name, element, error type and org ID. A link back to the error in Gearset is also provided enabling easy navigation from the ticket in Jira to the error details in Gearset.
The Jira ticket is displayed in the sidebar with its summary, created date, a link to the ticket in Jira, the assignee and its current status (e.g. In progress). If the ticket or status is updated on the Jira side, these changes will be reflected in Gearset.
Note: There may be a small delay before changes to the ticket in Jira are reflected in Gearset (~ 1 minute). You can manually refresh the ticket in Gearset to check for updates when they become available.
Creating an Azure Work Items ticket
Click on
Add Azure DevOps ticketSelect the
organizationSelect the
projectEnter a title for the ticket (required)
Enter a description to add details for the error
Click
Create work item
Clicking on the ticket number will take you to the ticket in Azure.
