Deploy Time metrics not showing up for REST API deployment events

[Andrew Harmon]

We have some repos linked to GitHub and some require using the REST api to post our build events. The GitHub linked show a Deployment Time metric, but the custom one does not. I assume it's some bug in the way I'm posting my deployment events via the REST api. I post a PENDING event with an updateSequenceNumber, then at the end I post a SUCCESSFUL event with a higher updateSequenceNumber and a a later lastUpdated date. deploymentProperties.sequenceNumber stays the same both posts. 

When looking at the timeline in Compass, I first see the pending event in the timeline, then when done, it's turned into a complete checkmark. So it seems the 2 events are being associated with each other correctly? But the Deployment time metrics show now events as you can see in the screen shot. Appreciate the help!!

[Enrique Serrano Valle]

Hi, @Andrew Harmon !

Based on your description, it sounds like you're using the right environments and sequence numbers, as you can see the deployment frequency being calculated.

Are you providing both `deploymentProperties.startedAt` and `deploymentProperties.completedAt` in your successful deployment events? You'd need to pass both so that the deployment time would be calculated.

[Tomislav Tobijas]

Hey @Andrew Harmon ,

I believe the Deployment Time metric is only automatically calculated for deployment events that meet specific criteria. For GitHub-linked repositories, Compass collects deployment events via the GitHub integration, specifically from GitHub Actions deployments that use a GitHub Environment name mapped to "Production" or "Staging" > here's the integration article

Now, this might provide some additional insights: Deployments not showing from Rest API 

Apart from ensuring that your deployment events and environment names are structured properly, and keeping in mind that deployment activity and metrics only appear if there has been at least one deployment in a production or staging environment within the last 28 days, not sure what else you could check 🤔

You could try checking if there's an open feature request or reported bug in JAC. (I did a quick sweep, but couldn't find anything related)

Atlassian folks might chime in on this and provide some better assistance.

Cheers,
Tobi