•  
     
    story #8321 Ability to move an artifact from one project to another
Summary
Empty
Ability to move an artifact from one project to another
As an example, there are different support teams in our organization using Tuleap, each team has their own project. For our users we would like to have a single point of entry. Based on the type of issue, we need the ability to move a ticket to a team that is using another project that will be responsible for resolving the ticket.

A couple of scenario's of how this feature would be used:

1) Basically we have multiple projects under one management. When User request a new feature or defect, the request will come thru one common channel. Later that request have to be moved to concern project for implementation. Teams will run their own sprints etc. and this request will be assigned under one of them. Currently we have to create a duplicate ticket or task to track the implementation. Thus the information is not transparent for the operations.

2) A feature could have multiple components to be implemented by different projects. They all belong to one grand Epic. If we separately create stories under each project, the link between the stories will be lost and the traceability at the epic level is not possible.

In short, the trackers in different project should behave the same as if it’s in one project.
Empty
Empty
Empty
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
#8321
Patricia Carrasco (pcar)
2018-03-07 17:07
2015-08-11 16:55
8443

References
Referencing story #8321
Referenced by story #8321

Follow-ups

User avatar

Moving is hard, structure will be different, there will be lost informations, people in CC / assignee / comment might not have access to the artifact, etc.

What do you think about more automation between artifacts / trackers / projects ? In both scenario we can imagine that one single ticket is linked / copied in other project.

For instance, for #1:

  • Automate creation of a new artifact in another tracker with a link to the original and maybe copy some field (summary, ...) 
  • Make artifact links association more flexible so we get rid of Tracker Hierarchy
  • Augment the trigger rules to report information to the original ticket or to cascade information from the original ticket downward

From the end user point of view, she just has one single entry point and she don't have to know / undestand where is the ticket now. What do you think ?

 

 

User avatar
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Could you detail the workflow you expect in such case ?
Which tracker(s), which informations are passed around (and not passed around), etc