Forum Discussion
Cycle time for a Spike incorrect
Hello,
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.
Garry
1 Reply
Seems only alternatvie ways still as below:
- Manually Adjust the State History: If you have the necessary permissions, you could edit the work item's history to reflect the correct state changes. This might involve setting the "Committed" state to the correct date in 2024. Be cautious, as this could affect other reports or metrics.
- Use Custom Queries: Create a custom query to filter out the specific Spike from your cycle time calculations. This won't change the cycle time in the widget but can help you generate more accurate reports.
- Leverage Analytics Views: If you're using Azure DevOps Analytics, you can create a custom Analytics View to exclude the problematic Spike or adjust the data to reflect the correct cycle time.
- Azure DevOps REST API: For more advanced users, the REST API can be used to retrieve and manipulate work item data. You could write a script to adjust the timestamps or create a custom report with the corrected cycle time.
