Skip to Main Content

Share your product feedback

Status Likely to implement
Categories Application
Created by Max Robbins
Created on Oct 10, 2024

Maintain proper estimate time unit when exporting/importing capacity estimates

What is the challenge?

Capacity detailed estimates in time can be in minutes, hours, days or weeks. When I bring the detailed estimate field into a list report, it includes the right time unit (ex 8h) but when this is exported to CSV, this field becomes just a number.

Then when I try to import this field as part of a CSV import, I have two options. Either I can import to "Detailed estimate" where it will treat this field as an estimate in minutes, or I can import to "Detailed estimate text" where I need to manually add the proper time unit as a suffix to every field.

What is the impact?

This means I either need to convert my exported detailed estimate to minutes, or I need to manually add a suffix to every estimate so it will import back into Aha! properly. Both these are manual changes to get your data into the expected format.

This is especially a challenge for teams needing to export their data from one Aha! account to another.

Describe your idea

Be able to export an initial or detailed estimate field so it could be imported to the "Initial/detailed estimate text" field. Maintain the unit suffix in the export so manual intervention is not required.

  • Attach files
  • +1