Page History
Section | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Example:
CreateCreate issue links
bybased on a custom field value avoiding duplicates
This is an example for creating specific In this example, issue links between issues with the same custom field value by avoiding duplicates.should be added avoiding duplicate links, e.g.
Given three issues with Imagine there are 3 tickets that have the same value for the custom field "Custom-ID": , Ticket A, Ticket B and Ticket C. When executing the transition on Ticket A, Ticket B and C should be linked to Ticket A. When now executing the transition on Ticket B, only Ticket C should be linked to Ticket B since Ticket A was already linked in the previous transition execution. For this the In order to add issue links on a transition, the Create issue link post function will be is used.
The configuration will look like this:
Text
to be parsed Issues returned by JQL expression is: key != %{00015} and XXXXX and Custom-ID ~ %{nnnnn12200} and key not in linkedIssues(%{00015})
Note that:
- %{00015} is the field code for field "Issue key"
- %{nnnnn12200} is the field code for the custom field XXXXX is the name of the custom field "Custom-ID" (this field code might differ on your instance)
Once configured, the transition will look like this:
See Result screenshots "Create issue links based on a custom field value avoiding duplicates"
Other examples of that function
Incoming Links | ||||
---|---|---|---|---|
| ||||
Related Usage Examples
Content by Label | ||||
---|---|---|---|---|
|