Changes to multiple components
Is there a best practice for managing a change which impacts multiple components? For example, when a defect requires a change to both the GUI and DATABASE components. This would result in two change sets being created, one for GUI and one for DATABASE. How could I ensure these change sets were related?
One answer
Best practice is to be working in the context of a work item. If you
are using the Eclipse client, and you set your current work to be that
work item, then the change sets that you create will be automatically
associated with that work item, and this will group the related work
items, whether they were from the same component or different
components. If you aren't using the Eclipse client (or don't like the
"current work" feature), then you are given lots of opportunities at
deliver time to associate your change sets with a work item.
Cheers,
Geoff
On 5/13/2010 12:23 PM, johna_owen wrote:
are using the Eclipse client, and you set your current work to be that
work item, then the change sets that you create will be automatically
associated with that work item, and this will group the related work
items, whether they were from the same component or different
components. If you aren't using the Eclipse client (or don't like the
"current work" feature), then you are given lots of opportunities at
deliver time to associate your change sets with a work item.
Cheers,
Geoff
On 5/13/2010 12:23 PM, johna_owen wrote:
Is there a best practice for managing a change which impacts multiple
components? For example, when a defect requires a change to both the
GUI and DATABASE components. This would result in two change sets
being created, one for GUI and one for DATABASE. How could I ensure
these change sets were related?