Edgewall Software

Changes between Version 1 and Version 8 of Ticket #5658


Ignore:
Timestamp:
Sep 10, 2008, 2:18:10 PM (16 years ago)
Author:
Christian Boos
Comment:

#7615 was closed as duplicate.

One of the issue here is how to store the change efficiently for all the tickets (see related discussion on this topic in #1890). Same problematic applies to #525 as well.

Also I think that adding a fixed comment like "milestone was renamed" or "retargeted after closing milestone", depending on the situation would be nice. In the future, this might even contain a link to the milestone version which triggered the change (for now milestone data is unversioned).

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5658

    • Property Cc th07@… added
    • Property Severity normal → major

  • Ticket #5658 – Description

    v1 v8  
    1 
    2 
    31 When I close a milestone and select "retarget open tickets" the tickets are successfully retargeted, however the change in milestone is not reflected in the ticket change history.