Your Token String may include a token for a JIS custom field (a custom field that is inctroduced by JQL Issue Select)
{issue.cf_12345}
In that case, the custom field token returns the issue object and the token can be followed by issue tokens explained in JIS v2.0 - Tokens Reference.
Using this capability, your JIS custom fields can reference each other and you can use field values of other issues (that are selected in other JIS fields) in your JIS field configuration.
Considering the data that can be kept on Jira issue fields and the flexibility of JQL language, the possibilities are endless.
Referencing issues selected in JIS Fields
Consider the following Jira issues:
| Issue Field | ABC-123 | ABC-124 |
|---|---|---|
| Key | ABC-123 | ABC-124 |
| Summary | My sample issue 1 | My sample issue 2 |
| Assignee | jack.black | mike.myers |
JIS Field A (with ID 12345) | ABC-124 | |
JIS Field B (with ID 23456) |
If you setup JIS Field B to have the following configuration, the calculated JQL Pattern for JIS Field A will be like:
JQL Advanced Field Config Setting | Setting Value | Calculated Setting for JIS Field B on ABC-123 |
|---|---|---|
| JQL Pattern | assignee = {issue.cf_123435.assignee} | assignee = 'mike.myers' |
This configuration effectively allows you to list issues in JIS Field B (on ABC-123) that are assigned to the assignee of the issue selected in JIS Field A (on ABC-123).
Everytime the selected issue in JIS Field A (on ABC-123) changes, the pick list for JIS Field B (on ABC-123) will also change accordingly.
Other issue field references can be used only for JQL Pattern in your field configuration. View Pattern setting allow you to reference the issue but does not allow you to reference other issue's fields for performance reasons.
For ex:
The token string {issue.cf_12345} can be used in both JQL Pattern and, View Pattern setting of your field config.
The token string {issue.cf_12345.assignee} can only be used in JQL Pattern setting of your field config.
Referencing multiple issues
If your JIS Field is configured to be a Label field with multi-select enabled, other JIS fields referencing this field can get values from multiple issues.
Once again consider the following Jira issues:
| Issue Field | ABC-123 | ABC-124 | ABC-125 |
|---|---|---|---|
| Key | ABC-123 | ABC-124 | ABC-125 |
| Summary | My sample issue 1 | My sample issue 2 | My sample issue 3 |
| Assignee | jack.black | mike.myers | stephen.fry |
JIS Field A (with ID 12345) | ABC-124, ABC-125 | ||
JIS Field B (with ID 23456) |
If you setup JIS Field B to have the following configuration, the calculated JQL Pattern for JIS Field A will be like:
JQL Advanced Field Config Setting | Setting Value | Calculated Setting Value for JIS Field B on ABC-123 |
|---|---|---|
| JQL Pattern | assignee in ( {issue.cf_123435.assignee} ) | assignee in ( 'mike.myers', 'stephen.fry' ) |
This configuration effectively allows you to list issues in JIS Field B (on ABC-123) that are assigned to one of the assignees of the issues selected in JIS Field A (on ABC-123) .
Everytime the selected issues in JIS Field A (on ABC-123) change, the pick list for JIS Field B (on ABC-123) will also change accordingly.
Referencing a chain of issues
JIS Field references can even be used in a chain to get field values from issues that are referenced on other issues.
Once again consider the following Jira issues:
| Issue Field | ABC-123 | ABC-124 | ABC-125 | ABC-126 | ABC-127 |
|---|---|---|---|---|---|
| Key | ABC-123 | ABC-124 | ABC-125 | ABC-126 | ABC-127 |
| Summary | My sample issue 1 | My sample issue 2 | My sample issue 3 | My sample issue 4 | My sample issue 5 |
| Assignee | jack.black | mike.myers | stephen.fry | hugh.laurie | rowan.atkinson |
JIS Field A (with ID 12345) | ABC-124, ABC-125 | ABC-126 | ABC-127 | ||
JIS Field B (with ID 23456) |
If you setup JIS Field B to have the following configuration, the calculated JQL Pattern for JIS Field A will be like:
JQL Advanced Field Config Setting | Setting Value | Calculated Setting Value for JIS Field B on ABC-123 |
|---|---|---|
| JQL Pattern | assignee in ( {issue.cf_123435.cf_12345.assignee} ) | assignee in ( 'hugh.laurie', 'rowan.atkinson' ) |
This configuration effectively allows you to list issues in JIS Field B (on ABC-123) that are assigned to one of the assignees of the issues selected in JIS Field A of issues those are selected in JIS Field A (on ABC-123) .
Everytime the selected issues in JIS Field A (on ABC-123, ABC-124 or ABC-125) change, the pick list for JIS Field B (on ABC-123) will also change accordingly.