| Summary | Milestone support |
| Queue | Whups |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Assigned |
| Priority | 1. Low |
| Owners | Horde Developers (at) , chuck (at) horde (dot) org |
| Requester | chuck (at) horde (dot) org |
| Created | 10/28/2008 (6205 days ago) |
| Due | |
| Updated | 10/28/2008 (6205 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | No |
data with them, but we should be able to have multiple milestones on a
bug, for instance (for bugs fixed in multiple branches).
State ⇒ Assigned
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Milestone support
Queue ⇒ Whups
Assigned to Chuck Hagenbuch
Assigned to
Milestone ⇒
Patch ⇒ No
on them, automatic roadmap generation, etc.
A thought: can we take queue versions and re-use them for this? I know
the version a bug is reported against is different from the one it's
fixed in (duh), but these seem like very similar things.