Out of office summary plan no longer works in 3.0 web
3 answers
Just to confirm, I see the same behavior in the most recent 4.0
milestone (i.e. the Eclipse plan can be used to show absences, but I
could not get Web UI plan to show absences).
Cheers,
Geoff
On 12/20/2011 10:38 AM, scottchapman wrote:
milestone (i.e. the Eclipse plan can be used to show absences, but I
could not get Web UI plan to show absences).
Cheers,
Geoff
On 12/20/2011 10:38 AM, scottchapman wrote:
I have a plan which we use to see team's scheduled absences using the
work around mentioned in WI 95801.
It appears to behave differently in RTC 3.0.1.1
In Eclipse the plan shows up as it did in 2.0.0.2 but on the web
nothing shows up.
Hello,
I am evaluating RTC v3.0.1 and I have found the following "strange" behaviour.
My project has a root Category and 3 child categories:
Unassigned (root)
I have created a Plan view "By Category" that displays the work items in a tree and grouped by category.
To my surprise, I have observed different behaviour of the "By Category" view if I open it with the RTC Eclipse client or if I use the Web Client.
The difference is that while the RTC Eclipse client does show the Category tree as expected (with one root node and 3 children), the Web Client surprisingly shows something like this:
Cat1
Unassigned(root)
Is this a known bug? I can not understand the resaon for this inconsistency otherwise,
regards
I am evaluating RTC v3.0.1 and I have found the following "strange" behaviour.
My project has a root Category and 3 child categories:
Unassigned (root)
- Cat1
Cat2
Cat3
I have created a Plan view "By Category" that displays the work items in a tree and grouped by category.
To my surprise, I have observed different behaviour of the "By Category" view if I open it with the RTC Eclipse client or if I use the Web Client.
The difference is that while the RTC Eclipse client does show the Category tree as expected (with one root node and 3 children), the Web Client surprisingly shows something like this:
Cat1
Unassigned(root)
- Cat2
Cat3
Is this a known bug? I can not understand the resaon for this inconsistency otherwise,
regards