πŸš€Β JWT 3.0 is outΒ πŸš€Β 

The app was completely overhauled, and so was the documentation:Β Jira Workflow Toolbox (Server/Data Center) Home

The page you are viewing is still valid for all app versions prior to 3.0.

On this page


Example: Triage Jira Service Desk email requests

The use of email requests in Jira Service Desk has one decisive disadvantage: only one request type (and therefore only one issue type) can be configured on a per email channel or per project basis.

In this example, a triage mechanism is configured for issues created via email, that are configured as request type Email request and issue type IT Help. If the summary contains the keyword "Incident" the request gets moved to issue type Incident and request type Email incident.

The recommended approach consists of two steps:

Add a global reflexive transition (from any status to itself) named Incident Triage.

In order to hide this transition from Jira users, add a Transition is triggered by Jira Workflow Toolbox post-function condition. Additionally, add a Move issues post function, with the following options:

  • Project β†’ Retain the project
  • Issue type β†’ Selected issue type β†’ Incident
  • Status β†’ Selected status β†’ Open (warning) must be a valid status present in the Incident's workflow
  • Additional fields, e.g.
    • Priority β†’ Standard β†’ Blocker
    • Customer Request Type β†’ Standard β†’ Email incident

(info) Additional fields aren't required, but at least Customer Request Type should definitely be set to ensure customers retain request visibility.

Once configured, the transition will look like this:

All the remaining post functions in this transitions are superfluous for this example and therefore can be deleted.

Next, add a Transition issues to the Create issue transition of the workflow attached to email requests - in this example IT Help - with the following options:

  • Target issue β†’ Current issue
  • Execute transition β†’ Incident Triage
  • Conditional execution

    %{nnnnn} = "move/b52566f1-6353-404a-98de-04e9a2a351a1" AND %{00000} ~ "Incident"

The field code nnnnn has to be replaced with the corresponding one for Customer Request Type (Customer Request Type Custom Field). To receive the exact value to match against, the easiest way would be to set this request type on an issue and evaluate with the help of our Expression Parser Test page.

(info) In the latest versions of Jira Service Desk, those request types consist of the project key, a forward slash and a hash value.

Once configured, the transition will look like this:

(warning) Ensure that Transition issues is placed after the Create the issue originally post function.

Once those two transitions are configured, requests created via email with the keyword "Incident" in its summary - which is the email subject - will be moved to the new issue and request type.



Related Usage Examples