Cycle time for a Spike incorrect

Copper Contributor



First time posting here. Hope this is the right place. Can you help please?


In Azure DevOps, we use PBIs and Spikes. We track the cycle time for each on a dashboard using the cycle time widget. 

What we noticed is a Spike, by mistake, had the State of “Committed” in 2023. But we didn’t actually do any work on it until 2024. We completed the spike in 4 days. But the actual cycle time is nearly 300!


Is there any way I can override, change or reset the cycle time for this item, please?


Any help would be greatly appreciated. 


0 Replies