Improve importers error persistence strategy
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Currently, Importer:Project Export/Import and Importer:Group Export/Import have the ability to persist errors during export/import in the ImportFailures table. This is helpful to provide to the user information about the failures that happened. This is also very helpful to support and professional services to debug imports in rails console, where they can do something like: project.import_failures.
Unfortunately, though, the same approach is not used in the other importers, which causes a disparity and difficulty in understanding when to use or not such feature.
Proposal solution
Normalize all importers to provide information about failures in the import_failures table. This way, regardless of what importer is being used we'll be able to easily se the any failures information in a centralized place. This might require some change in the import_failures table.