Issue Summary

When copying production data, especially large ones, the timer does not represent the actual time to complete the whole cloning.

Steps to Reproduce

• Go to admin.atlassian.com Select your organization if you have more than one.
• Select Products > Sandbox.
• Under Actions in the product table, select Copy production data.
• Choose copy with media files or without media files, select Copy data.

Related docs of the feature:
Manage product sandboxes
Early access feature

Expected Results

• The timer should accurately represent the time for the process to complete.

Actual Results

• Timer does not represent time to completion accurately and may present users with a wrong estimate

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available

As discussed with @vjadhav and 0da2b4edb1fb 

MCS team fixed the case where estimated time with attachment is turning out lower compared to estimated time without attachment which was a bug in estimation functionality. 

It is important to note that the estimated time is only an approximation and cannot be made 100% accurate. The actual migration involves factors that cannot be predicted in advance. As a follow-up action, we can request the team responsible for the UI to add a disclaimer indicating that the estimated times might not be entirely accurate and are intended solely as an estimate. So as to not cause any confusion to customer.