...
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, you can find the documentation heresee our JSU Cloud documentation. |
| Info |
|---|
The 'Linked Transition' feature is available from JSU 2.0 |
Description
This post function will trigger 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 2 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 | ||||
|---|---|---|---|---|
|
...
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 has have the necessary permissions, nothing will happen.
...
However, in some restrictive setup setups that user might not be allowed to do so on the related issue. He might not even see the project of the related issue!
With 'Perform Linked Transition as User' you can specify a different user account which 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 by in life persons.
...
A test case issue has several linked bugs. The bugs are linked as 'from test' to the test case.
Only when the the last bug is fixed, 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).
The prevent this transition to be executed already when the first bug is fixed, we configure here two statuses
...
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 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
This These fields will be copied to the linked issue, after the transition has been performed.
The conditions and validators of your linked transition will still use the old field values.
...
- Did you check the log files. There are cases , when the linked transition is not performed silently. But you will find a message in the log files on the server. You might increase to logging level (as described in 25680447).
- What happens when you manually click the linked transition. Does it work, or might there be a problem?
- Does this problem only happen by another user? Check that the user performing origin performing origin transition, also has enough 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 to be performed in an automatised way (with the 'Linked Transition' post function)?
- In the order of all post functions of the orign origin transition, the 'Linked Transition' post function must be the last one.
- Did you try to set a particular Resolution in the linked transition. ? Or with 'Resolution=empty' - does it then work?
- Did you check already the documentation above? You might find antoher another hint what to look for.