Modify ↓
Opened 14 years ago
Last modified 8 years ago
#7278 new defect
"Ticket Change" summary doesn't work if no milestone is assigned or milestone has no due date
| Reported by: | hju | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | ClientsPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.11 |
Description
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.
Attachments (4)
Change History (6)
Changed 14 years ago by
| Attachment: | send-client-email.no_milestone.xml added |
|---|
Changed 14 years ago by
| Attachment: | send-client-email.no_due_date.xml added |
|---|
result with milestone with no due date assigned
Changed 14 years ago by
| Attachment: | send-client-email.with_due_date.xml added |
|---|
result with milestone with due date assigned
Changed 14 years ago by
| Attachment: | summary_ticketchanges.py.diff added |
|---|
PATCH to change SELECT stament getting all tickets processed
comment:1 Changed 8 years 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 |
|---|
comment:2 Changed 8 years ago by
| Owner: | Colin Guthrie deleted |
|---|
Note: See
TracTickets for help on using
tickets.
result with no milestone assigned