Jira Status and Workflow syncingLast Updated: July 29, 2019
This article explains how Halp syncs the ticket status between the Jira issue and the Halp ticket, and how you can customize the behavior.
Jira projects come with workflows to enable status changes. Each project can have a different workflow as defined by your Jira settings, and different project types have different default workflows. The default Jira Service Desk workflow looks like this:
In Halp, to have these statuses show up on a ticket, you need to have a custom status with the same name, with a few exceptions. Halp defaults to "Open", "Pending", and "Closed".
For convenience, Halp maps the default Halp states and default Jira states in the following ways so you can get started without modifying anything:
To support other states in your workflow, create a Halp status with the same name as the Jira status. If a status does not exist and is not in the default mapping above, the status update will be ignored.
To create new Halp statuses, go to your workspace settings in Halp and go to "Custom Statuses".
In Jira, states are navigated to through transitions. Halp has a built-in understanding of the default Jira workflows for all issue types.
If you're using a custom workflow we need to teach Halp how to transition to different states. Send us your exported Jira workflow and we can configure your project to understand it.
To download your Jira workflow, navigate to your Jira project settings. Click on the Jira icon, go to Jira Settings, and then Issues. Click "Workflow schemes".
From this screen you'll see a list of your active workflows.
Click the pencil icon to edit the workflow, choose the "Export" dropdown and select "As XML".
Email or Slack us your workflow file and we'll configure your project.
You're now all set! Halp will use the custom workflow you uploaded to transition the Jira issue to the correct status to match the Halp status. Remember, for Halp to update the status it needs to exist in both Jira and Halp.