On 6/28/13, Matevž Bradač <[email protected]> wrote: > [...] >> >> Does anyone spot any other issues we need to worry about? > > Thanks for the feedback. I haven't started the discussion here > yet, since there are some blanks to fill in (mainly implications), > but I think that can be done in parallel. > > I assumed that moving the tickets from one product to another > would imply creating a new ticket in the target product, while > closing the one in the source product. This would of course mean > that the new ticket gets a new ID, while the old one gets a > reference (possibly a new duplicate/refersto relation?) so that > the old links would still effectively work.
JFTR , something like this is what I had in mind in my previous message when I said «Do not allow moving tickets to other products» > I don't know how > inconvenient this would be for the users, so perhaps we should > add your suggestion as a third alternative? > Good question . AFAICS at least nothing worse than what will be achieved now with two separate Trac environments, even if might be improved . -- Regards, Olemis.
