The validator Validation of linked issues is not yet available in JWT Cloud, but can be implemented easily using a Jira expression validator.
Migration steps
Add a Jira expression validator.
Build a matching Jira expression by migrating the parameters of the Validation of linked issues using this template:
let LT = [];
let ITI = [];
let SI = [];
let RI = [];
let P=[];
let FVE = (issueLink => issueLink);
let MI = 0;
let MA = 1000;
let LTA = false;
let ITA = false;
let SA = false;
let RA = false;
let FVEA = false;
let CON = (issueLink =>
(LT.length == 0 || LT.includes(issueLink.direction == "outward" ? issueLink.type.outward : issueLink.type.inward)) &&
(ITI.length == 0 || ITI.includes(issueLink?.linkedIssue?.issueType?.name)) &&
(SI.length == 0 || SI.includes(issueLink?.linkedIssue?.status?.name)) &&
(RI.length == 0 || RI.includes(issueLink?.linkedIssue?.resolution?.name)) &&
(P.length == 0 || P.includes(issueLink?.linkedIssue?.project?.key)) &&
FVE(issueLink)
);
issue.links.filter(CON).length >= MI
&& issue.links.filter(CON).length <= MA
&& issue.links.every(issueLink => (
CON(issueLink) ||
(LTA && !(LT.includes(issueLink.direction == "outward" ? issueLink.type.outward : issueLink.type.inward)) ||
(ITA && !ITI.includes(issueLink.linkedIssue?.issueType?.name)) ||
(SA && !SI.includes(issueLink?.linkedIssue?.status?.name)) ||
(RA && !RI.includes(issueLink?.linkedIssue?.resolution?.name))||
(FVEA && !FVE(issueLink))
)))
The following table shows how to obtain the individual components of the resulting Jira expression.
Migration details
|
Unknown AttachmentJWT DC |
JWT DC option |
Unknown AttachmentJWT Cloud |
Notes |
|---|---|---|---|
|
Filter by link type |
|
In line 1, add the issue link type names to be filtered to the list. |
Example: Bash
|
|
Filter by issue type |
|
In line 2, add the issue type names to be filtered to the list. |
Example: Bash
|
|
Filter by status |
|
In line 3, add the status names to be filtered to the list. |
Example: Bash
|
|
Filter by resolution |
|
In line 4, add the resolution names to be filtered to the list. |
Example: Bash
|
|
Filter by project
|
Any project |
Nothing to do! |
|
|
Current project |
In line 5, add |
Example: Bash
|
|
|
Any but current project |
In line 5, add Bash
|
|
|
|
Set projects manually (parser expression) |
In line 5, add project keys to be filtered to the list |
Example: Bash
|
|
|
Filter by field value |
|
In line 6, adopt the function according to your needs by adding the respective Jira expression. It has to return a logical value. A list of field codes can be found in Field codes. For more information about Jira expression, please have a look at Atlassian's documentation, the fields available for an issue links can be found in IssueLink. |
Examples: Bash
Bash
|
|
Minimum number of linked issues |
|
In line 7, change the minimum number of linked issues if necessary (the default is set to 0)
|
Example: Bash
|
|
Maximum number of linked issues |
|
In line 8, change the maximum number of linked issues if necessary (the default is set to1000) |
Example: Bash
|
|
Additional options
|
Allow unselected issue link types |
In line 9, change the value to true, if you want to allow unselected link types. |
Example: Bash
|
|
Allow unselected issue types |
In line 10, change the value to true, if you want to allow unselected issue types. |
|
|
|
Allow unselected statuses |
In line 11, change the value to true, if you want to allow unselected statuses. |
Example: Bash
|
|
|
Allow unselected resolutions |
In line 12, change the value to true, if you want to allow unselected resolutions. |
Example: Bash
|
|
|
Allow unsatisfied field value filter |
In line 13, change the value to true, if you want to allow an unsatisfied field value filter. |
Example: Bash
|
Validation options
This parameter is not available in JWT Cloud.
Error message
In JWT Cloud, only a fixed text without field codes or translations is supported.
Examples
|
Unknown AttachmentJWT DC parameter values |
Jira expression |
||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Use case There must be at least one related Service Management request
|
|
||||||||||||||||||||
|
Use case Prevent transitioning when there is a blocking issue
|
|
||||||||||||||||||||
|
Use case All blocking issues must be resolved
|
|