Issue Summary

When a deployment event is triggered via the GitHub for Jira integration, the integration fetches commits between the previous and current deployment tip to identify referenced Jira work items. Currently, this fetch is limited to a single page of 100 commits with no pagination, meaning any commits beyond position 100 are silently dropped and never processed.

This affects:

• Deployments panel: Jira work items referenced in commits beyond the 100th are never linked to the deployment.
• Release view: Commit traceability is incomplete for deployments with more than 100 commits.
• No error or warning is surfaced to the user; the deployment appears successful but is silently missing work item associations.

Steps to Reproduce

 1.  Connect a GitHub repository to Jira via the GitHub for Jira integration.
 2.  Trigger two deployments with more than 100 commits between them, where Jira work item keys are referenced in commit messages beyond position 100.
 3.  Navigate to the Jira Deployments panel or Release view on any of the work items referenced in commits beyond position 100.
 4.  Observe that those work items show no deployment association, despite the deployment completing successfully.

Current Behaviour

Only the first 100 commits between two deployments are fetched and processed. Commits beyond position 100 are never evaluated for Jira issue key references, resulting in silent, incomplete deployment associations.

Expected Behaviour

The GitHub for Jira integration should paginate through all commits between two deployments (not just the first 100), and process every commit for Jira work item key references. All matched work items should be linked to the deployment in the Deployments panel and Release view, regardless of how many commits exist in the deployment range.

Workaround

• Deploy more frequently to keep the number of commits between any two deployments below 100
• If performing a backfill doesn't repopulate the data, reach out to Atlassian Support for assistance