| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the JSU for Jira Server/Data Center documentation. If you are using JSU on Jira Cloud, see our JSU Cloud documentation. |
...
Description
This post function triggers a transition on a related issue. It can be very powerful in conjunction with the Create a Linked Issue post function to 'connect' the workflows of two issues.
...
The Transition Trigger Service provides also some functionality to trigger a transition on some issues. Depending on your use case you might use this post function or that service.
...
Configuration
...
...
Precondition
| Include Page | ||||
|---|---|---|---|---|
|
...
Trigger transition on all issues related as
You have several different options, on which related issue the transition will be triggered.
| Include Page | ||||
|---|---|---|---|---|
|
...
Transition
When the post function is performed, it will trigger the transition with that particular ID (51 in the example above) on the linked issues. If one of the linked issues uses a different workflow but has a transition with the same ID, that transition will be triggered. The name of the transition you see on the configuration screen does not matter. What matters is only the ID. If you want to trigger only the transition on one workflow, in that case, use the JQL scope and select the issues to transition with a query similar to issue in linkedIssues({issue.key}) and project = “PR Next Project”.
...
The transition on the linked issue will be performed as the same user, who triggered the transition on the origin issue. If he does not have the necessary permissions, nothing will happen.
...
Perform Linked Transition as User
If you don't specify anything here, the transition on the related will be performed under the same user, who triggered this post function on the origin issue. Thus that user must have the necessary permissions on the related issue.
...
With 'Perform Linked Transition as User' you can specify a different user account that owns the necessary permissions. Usually, this user account is assumed to be only technical, with broad permissions, but not used to log into Jira for normal activity.
...
Resolution
If any transition screen contains the resolution field, that field becomes mandatory. Here you have a chance to set a value for the resolution to be able to perform that transition.
Resolution here in the Post Function Configuration | Resolution on the issues at the beginning when the transition is performed | What happens? |
|---|---|---|
empty | (does not matter) | The resolution on the issue won't be changed. |
None | (does not matter) | The resolution will be set back to 'unresolved' (cleared). |
Any value | unresolved | The resolution will be set to the defined value. |
Any value | Any other value | The resolution won't be changed. |
...
All other sibling issues must have one of the following statuses
This allows you, that only 'the last' issue will trigger a linked transition.
...
If bug 3 in the above diagram is resolved, nothing will happen, because bug 4 still has another status (than Resolved or Closed). Finally, after that, bug 4 is resolved - all bugs now have the status Resolved (Closed would also be ok) - now the transition ('All bugs fixed (51)') on the test case is executed to set it to 'Ready for Re-Test'.
...
Copy fields
These fields are copied to the linked issue after the transition is performed. The conditions and validators of your linked transition will still use the old field values.
| Include Page | ||||
|---|---|---|---|---|
|
...
Supported field types
| Include Page | ||||
|---|---|---|---|---|
|
...
Position of the post function
You must put this post function after all other post functions in the same transition.
...
Example
See the Use Case Testing and Fixing Bugs for an example of how several of our customers use it.
...
Troubleshooting
If a linked transition does not get triggered, or it blocks your origin transition, these are a few things to check:
...