> The point is that ticket handling and management, the > social process surrounding tickets, is _broken_. > > I think it will be easier to fix that social process from something > closer to scratch. > > Thanks for providing me the opportunity to rant. Sorry for being > strident.
In general, I concur with your thinking on this. The process *does* need to be 'shaken up'. My concern is not with the process, but with the potential loss of important accumulated knowledge that may result. For example, it seems all to easy for ticket details to be mis- interpreted during manual migration and, once the new ticket exists, how diligent will people be to continue checking the old ticket system for relevant information? I suspect that most people, after perhaps a brief period of "dual- system use" will simply ignore the old ticket system and forget to check it. Given that people *today* aren't really using the Trac system propery (or at least not effectively), it seems likely that some tickets (especially older ones) will simply be forgotten or even outright ignored if they are only stored in a frozen, obsolete Trac ticketing system. Again, my suggestion is to automatically migrate the old tickets, but classify them in some manner as 'migration', without actually making them *active* tickets. When people search on the new system, it could still report tickets with previously noted relevant content, potentially including details of proposed, but *unimplemented* solutions to the problem. Then, they can create a fresh ticket with content either pasted from the older ticket, or by including a link in the new ticket content that points back at the old ticket. your thoughts? thanks, -e -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
