It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,841

question asked: Nov 30 '10, 5:30 p.m.
question was seen: 4,341 times
last updated: Nov 30 '10, 5:30 p.m.

Related questions

Work Items and Source Control integration misbehaving...

0
Jim Tykal (166●11●6) | asked Nov 30 '10, 5:30 p.m.
JAZZ DEVELOPER
Is anyone aware of changes to default behavior in the work item/source control integration in RTC 3.0? Here's what's happening:

When I perform a "Start Working" action on a work item, it does not automatically set the current work item. I can force it by clicking on the drop-down menu next to the work item ID and selecting "Set as Current Work Item", but it used to do this automagically when the "Start Working" action occurred.

Similarly, when I "Resolve" a work item that has associated Outgoing Pending Changes, I'm not prompted to Deliver them.

Is there a Preference somewhere that defines this behavior?

Thanks in advance for any insight...

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Yohko Tanaka (105●2●32●39) | answered Dec 21 '10, 2:35 a.m.
Hi,I faced the same situation.
I don't know whether this is "work as designed(behavior changed from v2?)" or defect. I've been investigating but couldn't find any information.

Did you get any information?
0
permanent link
Jim Tykal (166●11●6) | answered Dec 23 '10, 11:27 a.m.
JAZZ DEVELOPER
Hi,I faced the same situation.
I don't know whether this is "work as designed(behavior changed from v2?)" or defect. I've been investigating but couldn't find any information.

Did you get any information?


Haven't heard anything from the RTC dev team on this. Still unsure if it is a defect, a "feature" (i.e., works as designed, but changed from V2), or if it is some type of operator error on my part. I looked through Preferences and other configuration pages to see if it was now an option that had to be explicitly enabled, but did not find anything obvious.
0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Dec 26 '10, 7:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I believe this is "works as designed (behavior changed from V2)", based
on the V3 documentation.

Note the V3 documentation actually has a minor bug ... there is a
somewhat garbled statement "Open the work item and set its status to Set
as Current Work Item", which should probably say "right click the work
item and click Set as Current Work Item".

But I don't know why this behavior was changed in V3.
Perhaps someone from the source control team to comment on that?

Cheers,
Geoff

On 12/26/2010 6:12 PM, jimtykal wrote:
YOHKOTANwrote:
Hi,I faced the same situation.
I don't know whether this is "work as designed(behavior changed
from v2?)" or defect. I've been investigating but couldn't find
any information.

Did you get any information?

Haven't heard anything from the RTC dev team on this. Still unsure if
it is a defect, a "feature" (i.e., works as designed, but
changed from V2), or if it is some type of operator error on my part.
I looked through Preferences and other configuration pages to see if
it was now an option that had to be explicitly enabled, but did not
find anything obvious.
0
permanent link
Jim Tykal (166●11●6) | answered Dec 29 '10, 12:31 p.m.
JAZZ DEVELOPER
Thanks, Geoff.

I believe this is "works as designed (behavior changed from V2)", based
on the V3 documentation.

Note the V3 documentation actually has a minor bug ... there is a
somewhat garbled statement "Open the work item and set its status to Set
as Current Work Item", which should probably say "right click the work
item and click Set as Current Work Item".

But I don't know why this behavior was changed in V3.
Perhaps someone from the source control team to comment on that?

Cheers,
Geoff

Your answer

Register or to post your answer.


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.