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 #9564 move an basic artifact from one tracker to another (REST)
Actions
Summary
Empty
move an basic artifact from one tracker to another (REST)
Empty

Very first and limited implementation of the move:

  • No web UI yet (only REST route)
  • Duplicated fields limited to "Title" and "Description" (as per semantic)
    • Only the last value is transfered
  • If target workflow is not compatible, an error is returned (move impossible)
  • Create a new link (w/o type at this moment) between the source artifact and the target
  • Comments are duplicated (with owner & dates) but not the changes changes
Empty
Yannis ROSSETTO (rossettoy), Marie Ange Garnier (marieange)
Status
Empty
Canceled
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
#9564
Manuel Vacelet (vaceletm)
2018-03-07 17:06
2016-10-10 17:23
9837

References
Artifact links
Empty
Referencing story #9564

Artifact Tracker v5

epic #9563 Move artifacts from one tracker to another (base)
story #9565 moved artifact is linked with a type

Git commit

tuleap/tuleap/stable

REST route move artifact e0421c7fcc
User avatar Marie Ange Garnier (marieange) , 2016-12-08 15:25
Referenced by story #9564

Other

gerrit #6650
Display settings

Follow-ups