Dependencies are not updated in Advanced Roadmaps for Jira Plan
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Summary
Issues recently linked are not generating the corresponding dependency chain in Advanced Roadmaps for Jira (ARJ) plan.
Diagnosis
Run the following query into Jira's database, this will list all Issue Link Types in the instance:
SELECT * from issuelinktype;| id | linkname | inward | outward |
|---|---|---|---|
| 10,000 | Blocks | is blocked by | blocks |
| 10,001 | Cloners | is cloned by | clones |
| 10,002 | Duplicate | is duplicated by | duplicates |
| - | - | - | - |
| 10,300 | Block | is blocked by | blocks |
Then with the next query you will be able to see which Link types are configured as dependencies in ARJ:
SELECT ilt.ID, ilt.LINKNAME, ilt.OUTWARD, ilt.INWARD FROM ISSUELINKTYPE ilt
JOIN "AO_D9132D_DEP_ISSUE_LINK_TYPES" dlt ON dlt."LINK_ID" = ilt.ID;| id | linkname | outward | inward |
|---|---|---|---|
| 10,000 | Blocks | blocks | is blocked by |
You may compare both results, to verify if there are Issue Links with similar names that are NOT set as dependencies. In this example we see that we have both Blocks (ID 10000) and Block (ID 10300) link types and only the former is set as a dependency in ARJ.
Cause
The issue link type not set as a dependency is used in Jira, this is more likely when they have the exact same linkname value, albeit something not allowed to be configured by the UI, it could be created by a third-party plugin.
Solution
Either rename one of the Issue Link Types and Inward/Outward labels for something unique or delete the one with less usage. This can be confirmed on the Issue Link management screen, if you hit the DELETE button Jira will show how many times the chosen link is used throughout the instance and you'll also be allowed to replace it with another existing one:
NOTE: Before making any changes, please confirm if this Issue Link Type is not related to a third-party plugin. You might need to verify with the vendor for recommendations. Also, please follow best practices for Change Management:
- Test these steps in a lower environment
- Back up your system and data
This is to validate these changes and ensure that they will function within your infrastructure, prior to placing them in production. Finally, make sure that the changes are reflected in ARJ's dependency settings.