Provide clear and actionable steps when showing import failures to users
Problem
Error messages that we show under See failures
are not very helpful for users, because they are too generic and don't mean much to users.
Plus, the users don't know if and what they could do about them.
The customers that shared their feedback weren’t aware about the option to re-import the project via API. We should make it more clear in the docs and in the UI.
Soon there will be an option to re-import only chosen relations to the already existing project via API. We should document it and make this action available from UI, issue.
“Are we then able to re-run the transfer for just those projects that failed or do we need to export/import them individually? I'm a little unclear how the documentation around Direct Transfer and exporting.“
On the hand, there are some errors that cannot be fixed (an item cannot be written to DB because of validation errors and re-importing the project will still produce the same errors. That should be also clearly showed to the user.
Proposed solution
- Add subtext under the title of the page to better give users an idea of how to troubleshoot errors:
- Some failures can be resolved and the import retried. Learn more.
- Update the docs on how to reimport projects with the API: Add information for retrying migrations (!154856 - merged)
- When the
Title
of a failure is empty, use-
instead of empty space. - Change page title as per design.