[RTC6.0.1] Plan view widget displays error instead of progress bar
Hello,
I've a RTC 6.0.1 server running (no RQM nor RDNG, just RTC). In a "SCRUM" based project area, I've several "Sprint Backlog" plans. In each of these "Sprint Backlog" plans, I've a custom view that: - restrict the list of work items so that it only displays the WIs assigned to a particular user - groups WIs based on the owner - exclude empty groups - show the progress bar When showing the plan (not through the widget), no problems; I only get the WIs assigned to a particular user and see the progress bar (specific to that user). Now, when I present that same plan through a widget on the user's dashboard (using the "Plan View" dashboard), instead of seeing the progress bar, I see "Error" (have a look at attached screenshot). I get this error indepedently the dashboard is maximized or not. This is problematic since I'm looking for a solution to present on personal dashboard (for each project team member) the remaining capacity and personal progress and therefore hoped to use the progress/load bars. If you have suggestions using other widgets or means, they are welcome. If you can help me to resolve this problem, even better! Web browsers used: Safari, Firefox, Regards, Olivier
showing 5 of 8
show 3 more comments
|
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Btw. The problem is also applicable when the selected "plan view" is the default "Planned Time" that comes with the Sprint Backlog plan type.
I am also getting this error with a 6.0.1 environment.
Group by Team in plans with deferred load of plan elements and progress breaks progress bars for groups and shows error in plan view.
If I use the Web Inspector and look for errors on the page, I see the following messages:
It looks like this is different issue as the known defect. Have you tried different browser?
TypeError could be related to browser specific problem.
Same error message with Browser,
I have upgraded to 6.0.2 and this issue is resolved.