The Parent Links custom field is unusable
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
You can use Jira Query Language (JQL) to search for issues that use custom issue fields in Advanced Roadmaps. The Parent Link custom field can be used to search for child issues of an issue in Advanced Roadmaps. Under some circumstances the Parent Links field cannot be used.
Normally when the Parent Link field is included in your JQL search the name and custom field ID will appear in the suggestions below the search bar. The suggestions will not work when the Parent Links field is unusable.
Diagnosis
Environment
Advanced Roadmaps for Jira is installed.
- Jira Service Desk version 3.4.0 - 3.13.x is installed.
Cause
The bug JSDSERVER-4967 - JSD bundled plugins appear in User Installed Add-Ons causes some Jira Service Desk bundled plugins to appear as User Installed Add-Ons. As a result, bundled plugins that are required by Jira Service Desk may be mistakenly disabled or removed as they do not appear to be required. The querydsl-4.0.7-provider-plugin, for example, is also used by Advanced Roadmaps for Jira. Removing or disabling the querydsl-4.0.7-provider-plugin will break the Parent Links custom field, and JQL search cannot be used to find issues using the Parent Link field.
Resolution
Change Management
The steps required to resolve this issue may interrupt users accessing Jira. We suggest following best practices for change management and evaluating any changes that may impact users in a staging instance before completing the changes in a production environment.
To correct the issue, follow the steps below:
Install the latest version of Advanced Roadmaps (formerly Portfolio)
Re-index Jira (see Re-indexing after major configuration changes for additional information)
Confirm that the Parent Link field can be used