Example: Milestones for Server Operations should be listed as This week, next week, this month, next month, this quarter, next quarter, this year, future. And then we need a bit of magic [perl] that will calculate the time interval for it [displayed to the right of the milestone dropdown, or in it]. Target Milestone: [2001: January-March |v] Dropped down on february 14th it would be: 2001: January-March - This week (2/11-2/17) Next week (2/18-2/24) This month (February 2001) Next month (March 2001) This Quarter (before April 2001) Next Quarter (2001: April-June) This Year (2001) Future The time period would be calculated based on when the milestone is set. An alternative implementation could allow people to give an estimated number of days. The back end basically knows 3 dates: openwindow, setwindow, closewindow. For normal products openwindow would probably be >=setwindow, but for fuzzy things it's ok for it not to be. openwindow: the earliest something might be fixed setwindow: when the window for fixing this issue was set. closewindow: the latest this issue is expected to be fixed.

->Bugzilla product...

We need a simpler design: add a "delivery date" field to the milestones table, and provide the input space for it on the milestone editing page. Our use case: managers would like to see timeline of the project with outstanding and closed issues. Maybe it's feasible to add a parameter to enable dates for milestone, or tie it with the enablement of the time tracking facility in 2.18 (bug 24789).

Reassigning all of my "future" targetted bugs to indicate that I'm not presently working on them, and someone else could feel free to work on them. (sorry for the spam if you got this twice, it didn't take right the first time)

This is a little different, but see also bug 106363.

*** Bug 193658 has been marked as a duplicate of this bug. ***

Oops, I just realized in comment 4 that I noted the wrong bug. This is similar to bug 103636, not 106363.

Adds an optional 'deadline' date field to the Milestone object. If set, then milestones with the same sortkey are sorted by deadline.

Comment on attachment 493528 [details] [diff] [review] milestone deadlines v1 You are duplicating the existing Deadline field, which is unwanted here. Also, you don't need any customization to enter a date as milestone (it's just a string, after all).