On Aug 30, 2008, at 7:07 AM, Jennifer A. Drummond wrote: > On Fri, Aug 29, 2008 at 04:50:09PM -0400, Chris Nelson wrote: >> I want to create a milestone for urgent issues that sort-of always >> has a due date of today. I suppose I could make it due months ago or >> something and leave it perpetually overdue but that seems a little >> weird. Any thoughts? > > That's what we do, and yes, it does seem a little weird. I've argued > for > having it due way in the future instead, but then it shows up at the > bottom of the roadmap page instead of at the top; apparently my > opponents on this issue don't have "End" keys. ;)
This seems odd to me, too. In my opinion, the usefulness of milestones is that they group work based on time, and in so doing they provide a way to archive which work was done when easily. Making a milestone that always changes dates, or using one for a singular 'kind of' ticket like this defeats the point of using milestones in this way. > Personally, I'd rather not handle this situation with a milestone at > all, but rather with priorities. Since we do have a "future" milestone > that's our catch-all, it wouldn't be hard to institute a practice of > marking "hot fixes", and only hot fixes, as "critical". It would still > be trivial to create reports listing them. They wouldn't have a > presence > on the roadmap page; but what good does it do to have a graphical bar > for the "Ultra-Super-Urgent Tickets" milestone anyway, when it has 50 > long-closed tickets and 1 or 2 open things? This also kind of muddies the point of priorities, which to me make the most sense as a way to order one's workload *within* a certain timeframe, which is a milestone. In my company, we have a weekly or bi-weekly release cycle for most products. Hotfixes and absolutely urgent issues are simply placed into the milestone for the next maintenance release. They are then rated as critical priority fixes and we work on them ASAP. These bugs then get addressed at the next planned release. If any work doesn't get done in this milestone, those tickets are simply re-scheduled for the next release by moving them to the next milestone. Tickets without a milestone attached are known to be "unscheduled" work and get scheduled as needed by the tech lead or project manager/producer. In the case of an out-of-cycle release (such as an urgent security fix), we simply create a new milestone, set the date of that milestone to the planned hotfix release date, and chuck whatever tickets need to go into that release in that milestone. By setting that milestone's due date appropriately, it appears at the top of the Roadmap page. Communicating the urgency of this milestone can then be done with whatever convention your team uses. In other words, there's no law that says you can only use milestones for major point releases or something like that. A milestone can be whatever date-based event you want, major, minor, hotfix, or anything else that makes sense for your project. Cheers, -- -Meitar Moscovitz Personal: http://maymay.net Professional: http://MeitarMoscovitz.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
