Transition Trigger Service

Owned by IT Ops Notifications
Last updated: Jun 01, 2023 by Deborah Scott
3 min read

 

JSU for Jira Server/Data Center

This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation.

Description

This is a simple background job (Jira service) that triggers a transition on all issues that are found by a specified JQL query.

The Linked Transition and Follow Up Transition post functions also provide some functionality to trigger a transition on some issues. Depending on your use case you might use this service or those post functions.

Configuration

Add the service

See Atlassian's documentation for more information on how to configure Jira services.

Jira Transition Trigger Service

You must enter the following value as class:

ch.beecom.jira.jsu.jiraservice.TransitionTriggerService

Select the configuration options

Example transition trigger configuration as described in the cleanup example on this page.

User to run the JQL query and the workflow transition

Depending on the user who runs the JQL query, the result might be different. Not all users have the same permissions, so they might not see all Jira projects.

In production, it is a good idea to create a separate 'technical' user (not used by a real person), with a special name (for example 'automatic transition'). This will appear in the history of any changed issue.

JQL query

We recommend using a JQL query that returns issues only with a status that has a transition to the target status. Otherwise, it will not be possible to trigger a transition, and therefore, they remain in the result of the JQL query. Those remaining issues would then be unnecessarily processed again and again.

Target status in the workflow

The origin status of the issues does not matter. As long as there is a valid workflow transition to the specified target status, this will be triggered. If there is no valid workflow transition, nothing happens with those issues. Workflow conditions and validators might prevent performing the transition.

Example

Cleanup

In the example screenshot, users did not close all resolved issues. They will be automatically closed after 14 days.

Scheduled status change

Some of our customers use the transition trigger to schedule automatic status changes. 

Consider a workflow with the status Ready, the status Executed, and a custom field 'Execution Date/Time'. We then use the following parameters:

JQL query: status = Ready AND 'Execution Date/Time' <=  now() 

To trigger those issues the transition to the

Target status: Executed

In that transition, you might use a Webhook to trigger an action on an external system.

Known issues

This method is not supported in an UnloadableJiraServiceContainer

The following error message can appear during startup in the atlassian-jira.log file.

This only affects Jira Version 7.3.x during Startup. The Transition Trigger Service self is not affected after Jira successfully started.