Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      story #6854 copy artifact: direct simple copy
    Actions
    Summary
    tracker user
    copy artifact: direct simple copy
    Reference: story #6790
    • 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
    By Hugo KELFANI (hkelf)
    (733 kB)
    IMG_20140515_094433344.jpg
    Sequence_diagram_1
    By Hugo KELFANI (hkelf)
    (674 kB)
    IMG_20140515_094439577.jpg
    Sequence_diagram_2
    Patricia Carrasco (pcar), Emilio Palmiero (empa)
    Status
    Empty
    Done
    Development
    • [ ] Does it involves User Interface? 
    • [ ] Are there any mockups?
    • [ ] Are permissions checked?
    • [ ] Does it need Javascript development?
    • [ ] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [ ] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #6854
    Manuel Vacelet (vaceletm)
    2014-05-28 10:39
    2014-05-13 09:39
    3197

    References
    Artifact links
    Referencing story #6854

    Artifact Tracker v5

    rel #6686 7.1
    story #6790 copy an artifact (recursively if it has children)
    Referenced by story #6854

    Artifact Tracker v5

    story #6790 copy an artifact (recursively if it has children)
    Display settings

    Follow-ups

    User avatar
    Emilio Palmiero (empa)2014-05-15 21:27
    Agreed. Let's go ahead with the copy "without workflow enforcement" option.
    User avatar
    Manuel Vacelet (vaceletm)2014-05-14 16:33
    Patricia, Emilio

    After deeper analysis of the story, we think that doing a raw copy of the artifact snapshot sounds more natural than enforcing permission and workflow.

    Example 1: I copy an artifact with a field that I cannot see (permissions)
    - With workflow enforcement: the copied artifact will not have the field value
    - Without workflow enforcement: the field value is silently copied (ie. I don't even know it's copied)

    Example 2: I copy an artifact whose fields doesn't respect global state "Due date > Start date" (was created before the creation of the rule)
    - With workflow enforcement: I cannot copy the artifact without modifications
    - Without workflow enforcement: I can create the artifact with "bad" values

    We are considering going "without workflow enforcement" for copy, what do you think ?

    Manuel