What is the recommended means to revert the "Advanced Release Burndown"
Having just upgraded to 4.0.5 from 4.0.3 our users who have adjusted their thinking to the previous ABD chart (with all its warts and caveats) are now wanting to go back. I suggested that users could "Update from folder" should they have the RTC client earlier than 4.0.4 available.
One person claims to have done that and I can see that report resources were updated by her ( Recent events and the generic rpt query), but her claim is that nothing is different.
What's the best way to have both the report and micro reverted to pre 4.0.4 version ?
Ok, the user's are getting restless. Seems each day brings another problem report. I have 2 thoughts
One person claims to have done that and I can see that report resources were updated by her ( Recent events and the generic rpt query), but her claim is that nothing is different.
What's the best way to have both the report and micro reverted to pre 4.0.4 version ?
Ok, the user's are getting restless. Seems each day brings another problem report. I have 2 thoughts
- Using the 4.0.3 (or earlier) Advanced Release Burndown.reportdesign and Micro Advanced Release Burndown.rptdesign create new report resources with different than the default ID.
- Update the report design from a local file also from a v4.0.3 or older client
2 answers
I am using the workaround that you provided to me (first option, with a "different ID"). The micro report is not working in my dashboard widget but the full report seems to be nearly working (I am suspicious that I may have imported a different copy than the one I had previously been using.)