Why Merge requires a new workitem association?
RTC4.0.1 used.
Precondition is set to require work item and comments when delivering. There are two versions of changesets which were associated with workitems by two developers. Now the admin try to merge them and it complains there is no workitems associated for the merged changeset. Does the tool consider the merged changeset as a new one without a workitem association even though both of them were associated with the WIs before merge? |
One answer
Ralph Schoon (63.5k●3●36●46)
| answered May 24 '13, 7:36 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Don,
as far as I can tell, the original change sets are completed and can no longer be modified. Therefore it is necessary to create a new change set to merge. The tool can not, or does no, predict that the work item(s) linked to the old change sets should be pushed up. And in fact it would also be reasonable to have a new work item created for this integration, owned by the person merging. Comments Thanks Ralph.
Ralph Schoon
commented May 27 '13, 1:39 a.m.
| edited May 27 '13, 1:40 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Don,
The second approach changes the requirements for the special role of the integrator.
|
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.