Info |
---|
The 'Linked Transition' feature is available from JSU 2.0 |
Description
This post function will trigger
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
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 2 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
Position of the Post Function
You must put this post function after all other post functions in the same transition.
...
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 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 idID, that transition will be triggered. The name of the transition you see in the configuration screen actually does not really matter. What matters is only the id; only the ID. If you want to trigger the transition on only one workflow, 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 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 , no action will be performed.
Keep this in mind and design your workflows accordingly to prevent them to become sort of 'from becoming 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 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 happenfrom being performed.
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 setup that setups, the user might not be allowed to do so on the related issue. He might They may 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 personsfor 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.
Consider the following structure of linked issues from our Linked Transition 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 , 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.
The To prevent this transition to be executed already when the first from being executed before the final bug is fixed, we configure here two statuses:
Code Block | ||
---|---|---|
| ||
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 If 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 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
This These fields will be are copied to the linked issue , after the transition has been 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 position this post function after all other post functions in the same transition.
Example
See the Use Case Testing and Fixing Bugs for a nice an example , of how several some of our customers use it.
Troubleshooting
...
If a linked transition does not get triggered, or it even block 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
tothe 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 anotherto a particular user? Check that the user
performing originperforming the origin transition
, alsohas
enoughthe 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
to befrom being performed in an
automatisedautomated way (with the 'Linked Transition' post function)?
- In the order
Order of
allpost functions of the
orignorigin transition
,: Is the 'Linked Transition' post function
must be the last one.Did you tryin the final position?
Try to set a particular Resolution in the linked transition
. Or, or with 'Resolution=empty' - does it then work
?Did you check already the documentation above?
You might find antoher hint what to look for.