Connect the deployment to the issue
Issue identifiers in branch and commit context connect supported deployment events to the work they belong to.
Deployments
Bring Vercel deployment status and URLs onto linked Velocity issues so your team can follow a change after the pull request.
Illustrative workflow
Use the Velocity issue identifier in the branch or commit.
The connected account webhook sends the deployment’s status and context.
Open the linked deployment and inspect its result alongside the original task.
Issue identifiers in branch and commit context connect supported deployment events to the work they belong to.
Keep the deployment URL with the issue so reviewers can open the page they need to inspect.
Optional issue comments report terminal deployment status, with repeated events updating the same deployment record.
A workspace admin sets up a Vercel account webhook and stores the secret Vercel provides. Use issue identifiers in deployment branch or commit context and choose comment behavior in setup.
Choose the workspace and follow its integration setup. Your existing issue ownership, priorities and workspace permissions stay part of the workflow.
It receives Vercel deployment events and links their status and URLs to Velocity work. Your existing Vercel deployment process still starts the deployment.
Connect the tools your team uses to the work your team tracks.