Perforce changelists, on the issues they belong to.
A developer submits with GAME-412 in the description. Moments later that Jira
issue's development panel shows the changelist — author, description, file count. Nobody
links anything by hand.
We never touch your depot.
Most integrations ask for credentials to your version-control server. This one inverts that: your server pushes outbound to Jira, and there is nothing on our side to steal.
No credentials
Latchpoint holds no account on your Perforce server, and never connects to it. Your trigger authenticates to us with a secret you generate and can rotate.
No file contents
Only the changelist number, description, author, timestamp and file count are transmitted. No paths, no diffs, no source.
Cannot block a submit
Every failure path in the trigger exits zero. If we are down, unreachable or misconfigured, your developers keep shipping and never notice.
- Server credentials
- File contents and diffs
- Depot paths
description
author
timestamp
file count
- Inbound connection to you
- Firewall rule or open port
- Access to your depot
Three steps, about ten minutes.
Install from the Atlassian Marketplace
Open the admin page in Jira and copy your endpoint URL and secret.
Drop the trigger on your Perforce server
One script, two environment variables, no daemon and no inbound firewall rule.
LATCHPOINT_URL=<from the Jira admin page> LATCHPOINT_SECRET=<from the Jira admin page>
Register it with p4 triggers
That is the whole installation. The next submit carrying an issue key appears in Jira.
latchpoint change-commit //... "/p4/latchpoint-trigger.sh %change% %user%"
Built for teams who can't move off Perforce.
Game studios, VFX houses, hardware and automotive teams run Helix Core because nothing else handles hundred-gigabyte binary assets. Their work still lives in Jira. This closes that gap.
See the setup guide