Work Item related table option

Based on documentation, a couple of issues may arise when working in a team

  1. The subsequent save could overwrite the previous, potentially losing work.
  2. The conflicting saves could corrupt the project repository making your project unusable.

The first of the best practice indicates, one should always create work items for an object and its associated objects. In a large and complex development environment, this may be cumbersome.

It would be nice to have an option list for associated objects when creating a work item for an object. This list could be retrieved based on impact analysis and/or object relationships. Likewise the completion of a work item should be cascaded as well. This could help developers select multiple associated objects and create all work items at once without going through a series of layers and objects.

1 comment

Please sign in to leave a comment.