Bugzilla – Bug 76533
when error is given list possible causes/resolutions of the error
Last modified: 2011-05-05 06:29:51 UTC
Build : 0407 Description : When an error is returned to the user, ie a 500 error, produce a list of possible causes of the error. Also suggest possible solutions. This gives the user the ability to solve the problem better. Steps to reproduce : 1.kill mono on the iF3 server 2.login to the denali plugin notice the error that results 3. Expected Results : When a generic error occurs, or an error that is given that has several possible causes that the plugin cannot differentiate between, give a list of the possible causes and then suggest some possible resolutions, ie mono could be down, check the status of XSP or something like that. Actual Results : just the error code Additional information : Error reporting is starting to go this way in many apps. Not only does it report the error, but it also gives a possible solution and even the ability at times to solve the error from the error dialogue.
Changed to critical for inclusion FCS.
This is most likely too late for RC2, so I am moving to SP1.
Fixed on 5/10
this is not really fixed how I envisioned it. The error reporting is much better, but like I mentioned in the Expected Results section, I was hoping for a richer feedback to the admin user. ie; a list of possible causes and some steps that the admin user could take to debug the problem. changing this to minor since it is a new way of doing error reporting at novell.
reassigning to Rob since Scott left.
I agree that better error reporting would be nice.
Only enhancements that have been assigned to a release shall be marked as assigned.
Better error reporting has been implemented in the new version of iFolder Administrator.
Verified in oes2sp1 build so moving the bug to verified please close if reporter also agrees.
Closing this bug as per Comment9.Please reopen the bug if you find any issues.