Workflow Properties in Jira Service Management
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
We do not recommend manually configuring your Jira Service Management workflow properties. We introduced automation rules in Jira Service Management 2.4, which can be used to automatically transition issues when a comment is added.
Workflows in Jira Service Management are different from regular Jira applications workflows. Jira Service Management workflows have additional properties that Service Management uses to transition issues through the workflow. You may encounter problems transitioning issues in the customer portal if the workflow associated with a Service Management project does not have the properties mentioned below. As noted, we recommend using automation rules to make any workflow adjustments.
Workflow
- The "sd.workflow.key" property must be added to the workflow. This goes near the start of the workflow XML.
- The value of the property will be "sdItSupport" as seen in the example below
The following is a copy of the first few lines of an XML workflow. The property is added in the <workflow> prior to <initial-actions>
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE workflow PUBLIC "-//OpenSymphony Group//DTD OSWorkflow 2.8//EN" "http://www.opensymphony.com/osworkflow/workflow_2_8.dtd"> <workflow> <meta name="jira.description"></meta> <meta name="jira.update.author.key">tim</meta> <meta name="jira.updated.date">1420821503661</meta> <meta name="sd.workflow.key">sdItSupport</meta> <initial-actions>
Steps
- The "sd.step.key" property must be added to each step of the workflow in order for Jira Service Management to know who the request is waiting for (support or customer)
- WaitingForSupport = "sdWFSupport"
- WaitingForCustomer = "sdWFCustomer"
- Resolved = "sdResolved"
Actions
- The "sd.action.key" property must be added to each workflow action that will be transitioning the issue between statuses
- Adding these will cause Jira Service Management to automatically transition the issue when the customer adds a comment or when a Service Management Agent makes a comment directed toward the customer
- CustomerToSupport = "sdWFCustomerToWFSupport"
- SupportToCustomer = "sdWFSupportToWFCustomer"
CustomerToResolved = "sdWFCustomerToResolved"
- SupportToResolved = "sdWFSupportToResolved"
Default Service Management Workflow
- Here is a copy of the default Service Management workflow