Show incoming items does not display workspaces
![]()
RTC 2.0.0.2
Pending Changes view does not display Workspaces when 'Show Incoming items' or 'Show Outgoing items' is selected. When the user has multiple workspaces available in the RTC client (under 'My Repository Workspaces') these appear in the Pending Changes view as the top level of the folding tree. However when the user selects 'Show Incoming Work Items' or 'Show Outgoing Work Items' the top-level information about which workspace wil be affected is lost. This results in unwanted changes being made to streams or workspaces because the user inadvertently accepted/delivered changes for another workspace or stream. This is compounded by the twin evils of the 'Accept all incoming Baselines and Changes Sets' and 'Deliver all incoming Baselines and Changes Sets' ' buttons. If the user presses either of these buttons then changes can be done to al the workspaces the RTC cleint has in its list. Any idea? |
3 answers
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 16 '11, 9:10 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I'd suggest:
(1): Submit a work item, asking for "show incoming/outgoing work items" to display (2): Tell your users to either only display one workspace at a time in the pending changes view, or never use the Accept-All and Deliver-All buttons. Cheers, Geoff On 6/16/2011 4:23 AM, dwng wrote: RTC 2.0.0.2 |
![]()
Thanks Geoff. I feared this (2) would be the answer...
Anyone know if this is fixed in version 3? Cheers, David I'd suggest: RTC 2.0.0.2:oops: :oops: :oops: |
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 16 '11, 9:30 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
No, in 3.0.1, Show Incoming/Outgoing Work Items still shows all the work
items in a single list, even if they are coming from different workspaces. (I wouldn't have suggested creating a work item if it had already been fixed :-). Cheers, Geoff On 6/16/2011 7:23 PM, dwng wrote: Thanks Geoff. I feared this (2) would be the answer...:oops: :oops: :oops: |