Report Fields Consistency
The usage of various fields with respect to Migration Reports is not entirely consistent across ADMM.
For example, when saving a report that is flagged as an ‘Error’ Report Type, you get a warning about filling out the Business Impact and Recommendation fields, which makes sense. But as far as I can tell, those fields are not user-facing in both Migration Reports and Deployment Reports. The fields are not available in the ‘Choose Columns’ section when looking at all reports, and they do not show when you drill into the details of any individual report.
Another example is Report Priority. ADMM has values provided natively such as Major, Minor, Critical, Info, etc. These all make sense and can be very useful for cleansing. But, this field isn’t available anywhere in Migration/Deployment Reports, and it also isn’t available in the Report Import Template, making it nearly impossible to actually use.
It would be great if all the fields available when adding reports (Priority, Impact, Defect # etc.) were 1) available as a column to choose from in Migration/Deployment Reports, 2) showed in the details when you click into a specific report from Migration/Deployment Reports, and 3) were available in the Report Import Template.
Log in to comment and vote
Comments1
John Munkberg
May 1, 2025
The Business Impact and recommendation fields will appear in the Deployment Report details if they are populated. When they are blank the fields are hidden in the UI. It is not currently REQUIRED to populate these fields to publish an Error report, but it should be…..
I don’t recall WHY we decided to hide those fields when blank, so I’m open to feedback if we should change that, or make them hard-required in order to publish reports. I’m a FIRM believer that every single report should be reviewed and updated BEFORE it is published to a business user. Automated reports are NOT consumer grade out of the box. They often (always?) need additional context fields, order by, Business Impact, Recommendations, more verbose Descriptions, etc.
Agree PRIORITY has sort of lost it’s values over the years. We need to revisit the whole concept as part of our next phase of reporting. I agree there several gaps in our current reports - and PM is well aware of these and working to get improvements made. Thank you for your input, it’s always valuable.