Cycle time for a Spike incorrect

Seems only alternatvie ways still as below:

1. 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.
2. 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.
3. 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.
4. 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.