Duplicate key error when attempting to load the plan in Advanced roadmaps

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 11.3.7
    • Affects Version/s: 11.3.2, 11.3.3, 11.3.4
    • Component/s: ARJ DoS
    • 5
    • Severity 3 - Minor
    • 42

      Issue Summary

      A duplicate key error is thrown when attempting to load the plan in Advanced roadmaps because the same issue link id is being collected multiple times by the mapping function. 

      Add ability to handle merging duplicates in the mapping function.

      Steps to Reproduce

      Loom of Recreation: Reproducing Duplicate Key Error in ARJ Scenarios 

      Expected Results

      Duplicate key error shouldn't appear and the plan should load successfully

      Actual Results

      The below exception is thrown in the atlassian-jira.log file:

      2026-03-30 14:27:39,972+0000 http-nio-8080-exec-67 ERROR /rest/jpo/1.0/backlog [c.a.r.c.r.provider.exception.DefaultExceptionMapper] Duplicate key 419350 (attempted merging values com.atlassian.rm.jpo.core.issuelink.data.DefaultSimpleIssueLink@a2fcbc5b and com.atlassian.rm.jpo.core.issuelink.data.DefaultSimpleIssueLink@a2fcbc5b)
      java.lang.IllegalStateException: Duplicate key 419350 (attempted merging values com.atlassian.rm.jpo.core.issuelink.data.DefaultSimpleIssueLink@a2fcbc5b and com.atlassian.rm.jpo.core.issuelink.data.DefaultSimpleIssueLink@a2fcbc5b)
      	at java.base/java.util.stream.Collectors.duplicateKeyException(Unknown Source)
      	at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Unknown Source)
      	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(Unknown Source)
      	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Unknown Source)
      	at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
      	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
      	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source)
       

      Workaround

      Add the Jira dark feature flag:

      com.atlassian.portfolio.simpleplans.issueLinksFetchStrategyInClause.disabled

      Versions Tested

      Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: 

      Testing Requirements Version Affected Version
      Customers Reported Version 11.3.2, 11.3.3 Yes
      Most Recent Bug-Fix Release    
      Previous Major Release    
      Most Recent LTS 11.3.4 Yes
      Previous Supported LTS    
      Other Versions..    
      (Add rows as needed)    

              Assignee:
              Thomas Farr
              Reporter:
              Vijay Krishnan Subramanian
              Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: