User problem:

An issue can have many sprints allocated to them where some sprints might be removed from an issue.

Currently, the only way to JOIN the issue table with the Sprint table is by Joining them with the issue sprint history table. This makes it difficult to determine which sprints are currently allocated to the issue as the sprint history table records all sprints that were allocated to the issue (including the one that were removed from the issue). 

Suggested Solutions:

Add a direct link between the Issue table and the Sprint table. For example, the Sprint ID column should be available in the Issue table.

Workaround:

There is currently a Sprint field available within the issue custom field table which records the Sprint reference of the Sprint. This can be used to then map the issue with the sprint table.