"Ticket Change" summary doesn't work if no milestone is assigned or milestone has no due date
|Reported by:||hju||Owned by:|
The Summary "Ticket Changes" does not deal with tickets
- having no milestone assinged
- having a milestone with no due date.
This is cause a restriction in the SELECT startement in ´summary_ticketchanges.py´.
I´ve attached three excamples of the resulting xml-file. Only the version with due date shows the right result.
If I change the SQL-Statement (see attached diff), I could get the 2nd problem solved (tickets with milestones with no due date are now processed)
If there is no milestone assigned, any changes to the ticket won´t be added to the XML output - no idea why.
Change History (6)
comment:1 Changed 4 months ago by
|Summary:||"Ticket Change" summary does´t work if no milestone is assigned or milestone has no due date → "Ticket Change" summary doesn't work if no milestone is assigned or milestone has no due date|