When cloning an artifact, the user shall have the option to
- copy the associations
- copy the dependencies

by: Rudolf W. | over a year ago | Trackers

Comments

• Rudolf, can you please detail out the business use cases driving this requirement?

  by: Govind P. | over a year ago

• If an artifact is cloned the straightforward expectation is that everything is copied. So the question actually is: Why are the dependencies missing? Why should they not be part of the clone?
  
  A typical use case:
  A test case (activity tracker) depends on the requirement artifacts and is associated to the test specification document.
  The user needs a new test case.
  For this, the user clones the test activity. Actually he/she needs to check all dependencies and associations and recreate them, which costs a lot of effort.

  by: Rudolf W. | over a year ago