Issue Summary

Dependency API Calls return unexpected data for the "Needed By" field.

Steps to Reproduce

This issue can be observed by running a simple GET API Call on any Team Dependency.

For additional context, executing a GET API Call will typically yield a result similar to the following example:

{
    "id": 804,
    "title": "Test Dependency_72182655_6",
    "description": "Test Dependency_72182655_6",
    "releaseId": 765,
    "typeId": 1,
    ...
    "neededBy": null,
    "neededBySprintId": 4128,
    ...
    "committedBySprintId": 10749,
    "committedSyncSprintId": null,

Here, the "neededBySprintId" returns the Anchor ID instead of the Sprint ID if it is an Agile Team Dependency.

On the other hand, the "committedBySprintId" returns the Sprint ID.

When reviewing the Dependency on the Jira Align UI, the "Needed By" and "Committed By" values are identical, but different values are returned in the API, as detailed above.

Expected Results

Both the "neededBySprintId" and "committedBySprintId" fields should return the same value (Sprint ID) when accessed via API Calls.

Actual Results

The "neededBySprintId" returns the Anchor ID instead of the Sprint ID if it is an Agile Team Dependency.

Meanwhile, the "committedBySprintId" returns the Sprint ID.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.