I'm not sure how this would be implemented, but it doesn't make sense to copy ChangeSet and BuildRun information when copying a Story or Defect. These relations identify external effort tied to the source Story/Defect, not the target (usually).

Today, if one of our users copies a Story or Defect with associated Change/Build info, the user thinks we've done something wrong with our integration and come to us complaining that we're doing the wrong thing. Then we have to use the API to remove the ChangeSets, since that relation cannot be managed via the Web UI.

Comments

  • It would be helpful that when making a copy of a story, one could select the fields that are copied over. This could also be made configurable by Project, so that projects can specify the field that they consider mandatory.