Work Item not automatically associated with change set
On occasion, I have seen the following unusual behavior in the Pending Changes view. Developer starts working a work item. After making changes to source code, the change set is not automatically associated with the work item. As a workaround, I can manually drag the work item to the change set and associate. Is there a preference that is perhaps not set that is causing this behavior?
|
2 answers
|
I have a workaround for this behavior, but am hoping someone on the development team can assist me with a permanent fix. It seems that if I log out of my repository connection, then log back in, I get the proper behavior, with the work item is automatically associated with my changes. Unfortunately, when I close down my eclipse client and restart it, the behavior reverts back to the original behavior that I posted. Even though I have save password and auto-login, it seems like that capability may not be actually logging me in properly and causing the work item behavior, but that's just a theory at this point. Any help would be greatly appreciated.
|
This seems to be adressed in future versions. See defect 55850: Pending Changes new change set not getting assigned the current work item
Ben |
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.