Modify ↓
Opened 20 years ago
Closed 18 years ago
#1099 closed enhancement (wontfix)
Milestone statistics should not include invalid or duplicate tickets
| Reported by: | Christopher Lenz | Owned by: | Christopher Lenz |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | roadmap | Version: | 0.8 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
The statistics provided by the roadmap module for milestones currently include all closed tickets, regardless of resolution. To be more accurate, only tickets resolved as "fixed" should be included in the number of closed tickets.
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
| Status: | new → assigned |
|---|
comment:2 by , 20 years ago
comment:3 by , 19 years ago
| Milestone: | 0.9 |
|---|---|
| Severity: | normal → enhancement |
| Status: | assigned → new |
I don't see how do fix this currently because the set of resolutions can be changed by the admin. Postponing.
comment:4 by , 18 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
The typical solution to this is that tickets marked as "duplicate" or "invalid" simply should not have a milestone set. You can do this manually, or with the upcoming WorkFlow you could enforce it with a plugin.
Note:
See TracTickets
for help on using tickets.
That all depends, a ticket which is a duplicate shouldn't be counted as closed, but it shouldn't be treated as open ether.
Whet we need is a to ignore these tickets for the closed count _and_ for the total.
The same treatment should be applied to won't fixes among others