Dashboard migration logs should contain more information

Summary

Even if the migration of all dashboards is being performed with the usage of Dark Feature ( and dark features are experimental) as described in this public article , logging can be definitely improved as at this point it makes identifying the portlet/ gadget with dashboard association almost impossible.

Actual results

2024-01-23 09:40:37.707918386 WARNING CROSS-PROJECT-DATA project-import We couldn't import Portlet Configuration stats-gadget because of 2 missing dependencies: Custom Field 'xxxxxx', Filter 'xxxxxxxx'. But it will be migrated successfully if Custom Field 'xxxxx', Filter 'xxxxxxxx' are migrated later and the dashboards dependent on it will update accordingly in the destination site. Check the reasons for the missing dependencies on your server site.

Expected results

• As the log message does not provide details on identifying the dashboard that will not be rendered fine on cloud, migrators do not have an easy way of identifying which dashboards will have to be fixed post migration -> the same portlet can be used by multiple dashboards so in case migrator tries to migrate a considerable number of dashboards, the logging messages are useless;

Providing in the log the association between the portlet and dashboard ( name) would make fixing the dashboard in cloud easier -> manually verifying each dashboard is not a feasible operation when a considerable number of dashboards were migrated.