...
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server or on Jira Data Center, you can find the documentation heresee our JSU Server/Data Center documentation. |
Description
This post function will trigger 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.
You can also specify any number of fields, that will be copied to the related issue.
Configuration
Precondition
| Include Page | ||||
|---|---|---|---|---|
|
...
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 comment comments or fields are copied, no resolution is set.
...
The transition on the linked issue will be performed as the same user, who triggered the transition on the origin issue. If he does they do not has the necessary permissions, nothing will happen.
Resolution
It is important to keep the following in mind:
1) To set the resolution, It is necessary to have a resolve screen on transition. For more information, Please please see https://confluence.atlassian.com/jirakb/mapping-a-screen-to-a-workflow-transition-720634253.html
...
Consider the following structure of linked issues from our Linked Transition Post-Function27801825 use case:
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.
...
For general troubleshooting about JSU see Linked Transition .
If a linked transition does not get triggered, or it even block your origin transition, these are a few things to check:
- 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 Linked Transition).
- 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 the 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 of what to look for.