Page Comparison

...

Description

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

The 12681842 post function provides also 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 that those post functionfunctions.

Configuration

Add the service

See Atlassian's documentation for more information on how to confiugre JIRA configure Jira services.Image Removed

...

You must enter the following value as class.:

ch.beecom.jira.jsu.jiraservice.TransitionTriggerService

Define all paremeters

In the following screen, you can configure the details of the transition trigger service.

...

Select the configuration options

...

User to run the JQL query and the workflow transition

Be aware that depending 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 Jira projects.

In real production, it is a good idea to create a separate 'technical' user (not used by any a real humanperson), with a special name (for exmample example 'automatic transition'). This will appear in the history of any changed issue. With a separate 'technical' user with special name it is transparent for the end users of JIRA, what happened.

JQL query

...

JQL query

...

We recommend to use using a JQL query which that returns issues only with a status , which actually does have that has a transition to the target status.
Otherwise, it will not be possible to trigger a transition, and as a cause of thattherefore, they remain in the result of the JQL query. Those remaining issues would then would be unnecessary unnecessarily processed again and again.

...

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 to perform performing the transition.

Example

Cleanup

See the details of the above screen shot. Often people forget (or are too lazy) to In the example screenshot, users did not close all resolved issues. With the above configuration they They will be automatically closed after 2 weeks14 days.

Scheduled status change

Some of our customers are also using use the transition trigger to schedule some automatic status changechanges. 

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

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

To trigger on those issues the transition to the

Target status: Executed

In that transition, you might for example use some 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!.

[INFO] [talledLocalContainer] 2020-10-20 18:25:00,010 Caesium-1-4 ERROR anonymous    dadada [c.a.jira.service.ServiceRunner] An error occurred while trying to run service with ID '16900'. This method is not supported in an UnloadableJiraServiceContainer
[INFO] [talledLocalContainer] java.lang.UnsupportedOperationException: This method is not supported in an UnloadableJiraServiceContainer
[INFO] [talledLocalContainer] 	at com.atlassian.jira.service.UnloadableJiraServiceContainer.setLastRun(UnloadableJiraServiceContainer.java:86)

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