Issue Summary

Deployment events sent via the Jenkins for Jira (Official) Forge app are accepted by Jira (API returns SUCCESS_DEPLOYMENT_ACCEPTED) and are visible at the issue level (Development panel → Deployments tab), but do not appear in the project-level Development → Deployments view. Jenkins also does not appear in the project-level Tools sidebar.

Any customer whose site restricts anonymous access will be unable to see deployment data at the project level, despite data being correctly ingested. This affects the Deployments timeline, Deployment frequency metrics, and Tools sidebar visibility.

Steps to Reproduce

1. Have a Jira Cloud site with anonymous access restricted (standard security posture)
2. Connect Jenkins for Jira (Official) Forge app
3. Send deployment events via jiraSendDeploymentInfo with valid environmentType and state: 'successful'
4. Observe that issue-level Deployments tab shows data
5. Observe that project-level Development → Deployments view remains empty

Expected Results

Deployment data accepted by Jira and visible at issue level should also appear in the project-level Development → Deployments timeline view, regardless of whether anonymous access is restricted.

Actual Results

Project-level aggregation view does not display the deployment data because Data Depot's internal lookup uses a Service Principal that is blocked by the site's anonymous access restriction.

Workaround

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