Planned For automatically changes upon check-in
This occurs when someone checks in their code to a component. If the owner of the component is set to the team the person is on then everything works fine, but if the component is owned by the project (as are a number of components that span multiple teams) then RTC auto-changes the "Planned For" of the related work item to the current iteration of the project timeline. Is this yet another timeline-related bug? Or is there a setting somewhere that will stop the auto-change of "Planned For"? The history shows the proper creation of the record with the correct Planned For and above that is the change of Planned For that the user did not do.
2.0.0.2 ifix5 |
6 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Aug 30 '11, 6:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Are you sure this happens at "checkin" time? Usually, the only work
item manipulations happen at deliver time. And does this happen consistently, or only sometimes? Cheers, Geoff On 8/29/2011 8:38 PM, mshkolnik wrote: This occurs when someone checks in their code to a component. If the |
Are you sure this happens at "checkin" time? Usually, the only work Sorry, on Deliver. It is consistent when delivering to any component owned by the project (as opposed to a timeline) and the work item is Planned For a timeline other than the project timeline. |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 03 '11, 1:25 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In 3.0.1, I was not able to reproduce the behavior you report.
I'd suggest working with Rational Support. Is it possible that you have some custom process participant defined for this project? I'm not aware of any mechanism in any of the predefined process participants that would modify the Planned-For value as part of a Deliver. Note: I'm not sure what you meant by "as opposed to a timeline". A component can be owned by either a user, or a project/team area ... not be a timeline. Cheers, Geoff On 8/31/2011 7:08 PM, mshkolnik wrote: gmclemmwrote: |
Note: I'm not sure what you meant by "as opposed to a timeline". A Sorry again! I meant Team Area in that case, not Timeline. :) We have a Timeline for each major Team Area, so for us they aren't much different. |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Sep 07 '11, 12:55 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
OK, that now makes sense (:-).
Hopefully Rational Support can help you track this down ... and please post a followup with what you discover! Cheers, Geoff On 9/6/2011 8:23 PM, mshkolnik wrote: gmclemmwrote: |
|
I was able to work around this problem. There is a precondition on delivery called "Descriptive Change Sets" that has a setting for "Planned For" set to one of the following:
is optional is required (default) must be current iteration Despite the default being the second item and not the third, RTC was auto-setting the new work item to the current iteration of the main timeline, without bothering to notice the Filed Against category was associated with a team that's associated with a different timeline. I think it's a bug, but I can avoid the problem by switching the selection to "is optional". There was actually a warning on the Team Advisor tab that said "Assigned work item doesn't meet requirements " but the users hadn't noticed it. There was also a "Why did this happen?" link that told me where to look to fix this. |
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.