how does the traverse depth work for linkedIssuesOfAllRecursiveLimited

[neha agarwal]

Hi Team,

I have been struggling to make right use of the issue Function -> 

linkedIssuesOfAllRecursiveLimited. The traverse depth number goes until X but with what issue link type when not specified. for e.g.
in my simple opinion result of (X+Y =Z). Which is not the case in practical situation. 

X= issueFunction in linkedIssuesOfAllRecursiveLimited("project = 'XYZ' and type in ('Product User Story', nfr) and fixVersion is EMPTY and status not in (Rejected, Icebox)", 6)  and 

Y = issueFunction in linkedIssuesOfAllRecursiveLimited("project = 'HZN4: Platform Delivery' and type in ('Product User Story', nfr) and fixVersion is not EMPTY and status not in (Rejected, Icebox)", 6) 

Z= issueFunction in linkedIssuesOfAllRecursiveLimited("project = 'HZN4: Platform Delivery' and type in ('Product User Story', nfr) and status not in (Rejected, Icebox)", 6) 

I need help as this is required for my project's story points calculation, so there's business involved. 

[Layssa Souza]

Hi @neha agarwal 

Thank you for reaching out. Based on your explanation, all three queries seem to refer to the same project, varying only by how the fixVersion field is filtered:

X: Issues where fixVersion is EMPTY.
Y: Issues where fixVersion is not EMPTY.
Z: Issues without any condition on fixVersion.
Ideally, the results of X + Y should equal Z, but the discrepancy could be caused by:

Duplicate issues appearing in both X and Y.
The way linkedIssuesOfAllRecursiveLimited handles linked issues (e.g., link types).
How fixVersion is EMPTY and fixVersion is not EMPTY are interpreted (e.g., null or undefined values).
To assist further, could you clarify:

Are there duplicate issues between X and Y?
Are there specific link types expected in the results?
Could there be issues where fixVersion is null or not explicitly set?
With this, I’ll be happy to help refine the queries.

Best regards,