UNDO THIS! All but 1 active ticket assigned to me have been deactivated, and there are now only 10 active tickets in the database. All tickets by Milestone (including closed) only returns 180 items. Most of my tickets are now just gone including tasks that I created for myself. Please unroll these changes until you can figure out how to apply them without destroying the database. I missed the original discussion, but I do not want to lose the ability to create tasks marked as Ticket Type: task. On 3 Aug 2007, at 03:54, Juan Manuel Palacios wrote:

Hello everyone!

Not long ago some of us discussed on this list a new set of ticketing guidelines to match our current practices with Trac. The result of such brainstorming was the Wiki doc I compiled at [1] and which Mark has been fleshing out into the new guide at [2]

After much waiting I finally went ahead and implemented most of what's said there through Trac's admin interface, so everyone should now see new fields in new ticket submissions per the new guidelines. Legacy fields need to be updated directly in Trac's database through SQL magic as follows:

1) Ticket Type: * task & contribution --> enhancement;

2) Priorities: * Expected --> Normal; * Important & Blocker --> High; * Nice to have --> Low;

3) Component: * dp-cocoa & uninstaller --> deprecated;

Chris Pickel suggested the following template:

1) * update ticket set type='enhancement' where type='task' or type='contribution'

2) * update ticket set component='deprecated' where component='uninstaller' or component='dp-cocoa' * update ticket set priority='High' where priority='Important' or priority='Blocker' * update ticket set priority='Normal' where priority='Expected'

3) * update ticket set priority='Low' where priority='Nice to have'

I can ask kvv to apply this for us straight into the DB, but would love it if they could be verified to work (I don't have Trac installed at the moment to test locally).

New Roadmap is also in place, with new self-explanatory "MacPorts base enhancements" and "MacPorts base bugs" milestones created to hold tickets detailing MacPorts' own bugs and improvements separately, mirroring "Port Enhancements" and "Port Bugs" respectively. We toyed for a while with the idea of using the "core" moniker rather than base, arguing that the latter might be a bit confusing.... but I ultimately stuck with base 'cause I figured we prefer people who are clueful enough to figure out what "base" stands for in MacPorts parlance as the ones submitting tickets against such a, eeehhmmm, core component of the project. Added to that is the fact that "base" is already all over the place, so it only makes sense... Tickets in the former "Needs developer review" milestone were moved to base bugs and "Feature requests" to base enhancements; please feel free to relocate your ticket appropriately if you feel this reordering does not do it justice.

Thanks to all who helped polish such an important user <--> developer interface as the ticketing guidelines! If you have suggestions and/or corrections (am I missing anything here in this message? I surely am, it's 4am ;-).... you know what to do, *cough* ticket per the new guidelines *cough*.

Regards,...

-jmpp

[1] http://trac.macports.org/projects/macports/wiki/NewTracTicketing [2] http://geeklair.net/new_macports_guide/#id942789 _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev

Randall Wood rhwood@mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."

On Aug 3, 2007, at 6:03 AM, Randall Wood wrote:

On 3 Aug 2007, at 05:53, Randall Wood wrote:

...

UNDO THIS!

All but 1 active ticket assigned to me have been deactivated, and there are now only 10 active tickets in the database. All tickets by Milestone (including closed) only returns 180 items.

I was able to find 6000+ tickets using a custom query, but still, can you revert this change until you figure out how to do it without closing every single affected ticket?

If I do a custom query for my not closed tickets, I find all my open tickets, but for some reason they are considered inactive, and do not show up in report 8 "Active tickets (mine first)"

...

Most of my tickets are now just gone including tasks that I created for myself.

I found them but they seem to be in some strange limbo land. See above.

I'm sure this is nothing to worry about, I'm positive actual tickets have actually *not* been affected in any way (you can for example browse the roadmap, actually diving into each milestone, and realize there are many more than just 10 active tickets in the database). I believe the only thing at fault here is Trac's ability to query its db for tickets on an automated fashion through the reports facility, given how some of the fields changed per the new guidelines. Each report is just an SQL statement (that we can thankfully tailor to our needs), so I'm sure what we need to do is figure out how they broke and thus edit them. Can you please provide me the queries that worked for you in order to compare? Thanks for your feedback! Regards,.... -jmpp