| 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 The Linked Transition 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.
You can also specify any number of fields , that will be copied to the related issue.
The Transition Trigger Service provides also some functionality also allows you to trigger a transition on some issues. Depending on your use case you might use this post function or that consider using this service.
...
Configuration
...
...
Precondition
| Include Page | ||||
|---|---|---|---|---|
|
...
Trigger transition on all issues related as
You have several different options , to define 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 1 in the example aboveconfiguration) 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 only 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”.
If the transition with that ID is not available on the linked issue (probably because it is in a different status) nothing will happen. Also, no comments or fields are copied, and no resolution is set.It is important to keep , no action will be performed.
Keep this in mind and design your workflows accordingly to prevent them from becoming sort of ' out of sync'. You might also could use several 'Linked Transition' post functions in the same transition, each calling a different target transition, to match possible different statuses of the linked issue.
Also be aware, that there might be some consider workflow conditions or validators , which that could prevent a transition from being performed.
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 That user must have the necessary permissions on the related issue otherwise nothing will happen.
However, in some restrictive setups, the user might not be allowed to do so on the related issue. They may not even see the project of 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 |
|---|
in the Post Function |
|---|
configuration | Resolution on the issues at the beginning when the transition is performed | What happens? |
|---|---|---|
empty |
any | The resolution on the issue won't be changed |
None |
any | 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, permits that only ' the last' final transitioned issue will trigger a linked transition.
...
Only when the last bug is fixed , should the test case should be set to the Status 'Ready for Re-Test' (this is the transition 'All bugs fixed (51)' in the above screenshot)status.
To prevent this transition from being executed already when before the first final bug is fixed, we configure two statuses:
| Code Block | ||
|---|---|---|
| ||
All other issues linking to the target must have one of the following statuses: Resolved, Closed |
...
If bug Bug 3 in the above diagram is resolved, nothing will happen, because bug Bug 4 still has another a status (other than Resolved or Closed). Finally, after that, bug . When Bug 4 is resolved - all bugs now have the status Resolved (Closed would also be ok) - now the transition ('All bugs fixed (51)') , the transition 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 must position 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 some of our customers use it.
...
Troubleshooting
If a linked transition does not get triggered, or it blocks your origin transition, these there are a few things to you can check:
Did you check the log files? Log files: There are cases when the linked transition is not performed silently. But , but you will find a message in the log files on the server. You might increase the logging level.
What happens when you manually click the linked transition? Does it work, or might there be a problem?
Does this problem only happen to another a particular user? Check that the user performing the origin transition also has enough the necessary permissions for the linked transition.
Is there a transition screen for the linked transition? Is there any condition, validator, or post function on the linked transition? Could these prevent the transition from being performed in an automatized automated way (with the 'Linked Transition' post function)?
In the order Order of all post functions of the origin transition, : Is the 'Linked Transition' post function must be the last one.Did you try in the final position?
Try to set a particular Resolution in the linked transition? Or , or with 'Resolution=empty' - does it then work?