I’ve attached an example of a CSV file I’ve used to test Aha’s import functionality (comes from a dev system being used). The challenge is that the export gives features across various releases and the current import functionality in Aha requires us to import features per release.
Is it possible to import a CSV file in a way that Aha is able to identify each feature uniquely and update all the other information as required (releases, tags, statuses, etc.) without us having to create separate CSV files for each release. The import will be done to get the features into Aha the first time and thereafter to keep the information in Aha up to date.
Hi there, this idea was shipped some time ago. Now when you are importing features via CSV, you can include a release ID in the CSV file. This means that you can import features across multiple releases. This article explains importing via CSV in more detail. Thanks!
What does shipped meant as i don't see any responses for the question.
I'm running into this now... I'm trying to update status and estimates from features/stories in the development system. It is a lot of work to have to create an import file and process it for each unique product/release combination.