After first round of discussion / grooming with the team we propose to split the story in 3:

Direct simple copy (8 pts)

• Note: technicaly speaking, use XML as intermediate format to avoid future DRY (1st step for full import/export of tracker v5)
• When I'm on the artifact, I can select "Copy this artifact"
• Then I'm redirected on a new view (like artifact creation) but filled with values of source artifact
• When I hit "submit" the new artifact is create in real time
• History is no conserved (copy is a snapshot)
• Handeling of special cases
  • Artifact links: field is empty, we don't copy the links
  • Attachments: we only see there is one (with file name and desc but no preview)
  • Back links are not conserved (ex. I copy a user story that is referenced by an Epic and a Sprint, the copied artifact is not linked to them)
  • If workflow forbid the new artifact (because rules changed or because the current state is incomatible with an artifact creation, the copy cannot be submitted (values must be changed before copy submit)
  • "Submitted on" and "Submitted by" are set to current user and current time (ie. the copied artifact is created NOW by MYSELF)
  • Assignee/Submitter/CC are notified
  • Post actions & triggers applies
  • There is a follow-up comment with a link to the original

Recursive copy (5 pts)

• Based on previous story
• Introduce the recursive copy of children only (other links are not conserved)
• There is an hardcoded limit of the number of children that can by copied (to be defined) if the limit is reached, there is a message telling that only part of the children will be copied (prevent page too long to load, see next story)
• There is no "Update" screen for the children, they are copied "as is"
  • We cannot select which ones (not displayed either, just a message telling that X children will be copied)
  • There is an option not to copy children (instead of displaying artifactlinks field)
• For children copy, same limitation applies than for "Direct simple copy"
  • if the children cannot be copied, there is an error and it's skipped
  • if a "parent node" (when there is more than 1 level) and the parent cannot be create, all its childrens are skipped
  • at the end of the process, I have the list of errors (not copied artifacts). It's added as a follow-up of the copied artifact (by Worklfow Manager user)

Huge hierarchy copy (3 pts)

• Based on previous story
• When the number of artifacts to copy is below the defined threshold, nothing change
• When the number of artifacts to copy is above the defined threshold, the copy is processed in background (system event).
• The parent is created "on line", the background process only applies on children
• The copy is done the same way
• When it's done, a mail is sent to the user who did the copy to inform about the status (success and failures)

Does it makes sense ?