Project Configurations for Related Issues

Each project can have its own set of “related issue” definitions. Project level related issue definitions can only be created by project administrators and available for all users within the context of project’s issues. Of course, users can also define their own issue level related issue configurations. On the issue view, users can switch between different “related issue” definitions.

Open

Title: Title displayed on the “related issues” section of issue view.

JQL: A parametric JQL which specifies related issue criteria. This JQL is evaluated within the context of current issue. You can use issue fields by using “$issue.field” syntax. It should be a valid JQL, and you can use auto complete features when editing it.

Fields: You can specify additional fields that will be displayed as columns on the “related issues” table of issue view.

Number of issues: You can specify number of issues displayed at once. You can navigate between different set of issues using “Next” and “Previous” buttons on the “related issues” table.

Open

Some Example Configurations

Organizations field stores the organizations that are associated with a Service Desk customer portal request. When the Organizations in ("$issue.cf[10300]") JQL is used, the generated title shows issues with the same value for the "Organizations" field of the displayed issue. As shown in the table below, you can view the status, the time to first response and the time to resolution of issues with the same organization value by adding corresponding fields to the ‘Fields’ part.

Similar to the example above, you can view the other issues that are fixed in the same version with the version the displayed issues has by using the JQL fixVersion="$issue.fixVersion". Also, you can view the status of the issues in this fix version by adding status field to 'Fields' part.

Please refer our “Example Use Cases” page for more samples.