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 here. |
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.
You have several different options, on which related issue the transition will be triggered.
When the post function is performed, it will trigger the transition with that particular id (31 in the example above) on the linked issues.
When the post function is executed, it will just look if that transition id is available on the target issue. No matter what workflow and transition name you picked in the configuration screen (that is only to make it easier to find a particular transition id during configuration).
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 or fields are copied, no resolution is set.
It is important to keep this in mind and design your workflows accordingly to prevent them to become sort of 'out of sync'. You might also 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 workflow conditions or validators, which could prevent a transition to be 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 has the necessary permissions, nothing will happen.
It is important to following in mind:
1) To set the resolution, It is necessary to have resolve screen on transition. For more information, Please see https://confluence.atlassian.com/jirakb/mapping-a-screen-to-a-workflow-transition-720634253.html
2) 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. |
Any value | Any other value | The resolution will be set to the defined value. |
This allows you, that only 'the last' issue will trigger a linked transition.
Consider the following structure of linked issues from our Linked Transition Post-Function 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
All other issues linking to the target must have one of the following statuses: Resolved, Closed
(Resolved is not visible in the above screenshot, but actually selected further down in the list of 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'.
This 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.
See the Use Case Testing and Fixing Bugs for a nice example, how several of our customers use it.
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: