#14 move messages between tickets

open
nobody
None
5
2003-10-29
2003-10-29
No

I have added the ability to move messages from one
ticket to another (see attached patches).

It often happens in practice, that a new ticket arrives,
which belongs to an existing ticket, or the other way
round, that a mail is assigned to an existing ticket,
which should be better a new one.

In the start field of the form enter a python index (0 ...
first message, 1 ... second, -1 ... last, -2 ... before last).

The form appears on the MailManager instance home
page. A totally inappropriate place. It is a quickshot, but
moving messages makes our life with MailManager so
much easier.
Hopefully a similar feature with adequate presentation
layout will be included in one of the next releases.

Discussion

  •  
    Attachments
  • Logged In: YES
    user_id=881094

    Here is a version with adequate layout (*.patch1
    attachments)
    Moving messages form is included in the
    ticket_index_html.zpt

     
  •  
    Attachments
  •  
    Attachments
  • Logged In: YES
    user_id=881094

    I have attached the MOVE MESSAGES feature for the current
    CVS version (11-12-2003), which seems to be nearly 1.00
    (files containing -1.00).

    Further it enables the user to select an arbitrary message for
    citing in the response text area, instead of using the
    hardcoded first one.

     
  • Logged In: YES
    user_id=687101

    Sorry for delay. We agree that this is a needed feature.

     
  • Andrew Veitch
    Andrew Veitch
    2003-12-14

    Logged In: YES
    user_id=753066

    I'm sorry we've taken so long to comment on your patches. Thanks
    very much for the work. I think it would be good to get this into
    version 1.0.

     
  • Andrew Veitch
    Andrew Veitch
    2003-12-22

    Logged In: YES
    user_id=753066

    I've looked at this in some detail and I've also looked at how
    competing products handle ticket merging.

    The approach I've adopted is to properly implement the parent
    ticket/child ticket functionality that was already there. So lets say
    ticket 50 and ticket 60 should be merged, the procedure is to
    make ticket 60 a supporter of ticket 50 and then close ticket 60.

    This isn't as flexible as the patch you've submitted but it has a
    more simple interface. My code is now in the CVS.

    I'm leaving this RFE open for now because we also need to look at
    improving the message citation.

     
  • Logged In: YES
    user_id=881094

    I was a little more happy with MOVE MESSAGE, especially
    in the case of splitting a ticket instead of merging: if
    a message should be better a new, separate ticket, than to
    be assigned to an existing one.