-
Suggestion
-
Resolution: Unresolved
-
None
Description:
Currently, teams using Perforce with Jenkins for Jira or other integrations can only link build jobs to Jira issues, not individual Perforce changelists. This is a significant limitation for teams using Perforce as their primary VCS, as the Development panel in Jira only displays build links and not the underlying changelists/commits, unlike Git integrations.
Request:
- Native support for displaying Perforce changelists as individual 'commits' in the Jira Development panel, similar to how Git commits are shown.
- This should not require FishEye/Crucible, but instead provide direct support via Jira Cloud (either through a public API or plugin integration).
- The solution should allow Jenkins or other CI/CD tools to map Perforce changelists to Jira issues so they appear in the Development panel.
This functionality is critical for traceability and developer productivity in Perforce-based teams.