Migration to / from Kunagi (Data Import / Export)
As a project administrator, I want to be able to import CSV data from another tracking tool, in order to migrate to kunagi easily and without the need to rewrite all my trackers
Statement from Kunagi Team
Current workaround: All stories are XML files in the data direcotry entities/requirement/. You can generate these while Kunagi is stopped.
sto185, sto186 somewhat cover this by providing Read/Write-API for Kunagi that can be used for ex- and import.
Status
Issue is closed.
Comments
Tue, Mar 26, 2013, 12:19 by Aruna Gutta
Is it possible to provide option on Kunagi GUI to export the Issues data into CSV file?
Also, We have OAT team that validates the product before release. We would like to categorize those and issues found by customers as post release issues/bugs. How can we do that (OAT team and customers are not part of SCRUM team, they don't access Kunagi, so the issuer field will not help). Ability to identify these issues helps us track how many and what issues/bugs fell through the cracks.
Between, thanks for fixed iss972.
Thank you.
Tue, Mar 26, 2013, 12:33 by artjom (PO,T)
For export/import we have the plans mentioned in the Description and Statement. Once that is done, developing plugins for different formats should become easier. However, we do not have any solution for this right now.
Do I understand correctly that you want to classifiy Tasks into two categories: Issues posted by users and Issues posted by your OAT team?
Requirements like these are always hard to do. We try to limit the UI to the important core elements that should in a way or another be needed by every Scrum team. Introducing additional fields for specific scenatios would rather quickly clutter the UI. I cannot come up with a better solution than to use an existing field to make a note, like in the Description. Would it help to make the Issuer field editable?
Tue, Mar 26, 2013, 13:06 by Witek (SM,T)
Also note, that Kunagi can generate a homepage for you, where your custorers (or someone else) can post issues. The issuer-field is then filled with the data provided by the issuer. kunagi.org is an example.
Tue, Mar 26, 2013, 13:08 by Aruna Gutta
Yes, Can you make issuer field editable.
Another question, is there going to be any filtering options added issues?
So that I can filter on issuer, severity.
Tue, Mar 26, 2013, 13:27 by Witek (SM,T)