[Trac] svn changeset as Comments
Hi, Im looking for a way to push the svn changeset (with commit log as the body) as a ticket comment, so that I can see the actual comments on the ticket and also the commit logs. I have looked at the default plugins and couldn't find a way to do this. Any help in this is much appreciated. -- Sandeep --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Requirements for a new and improved Gantt plugin
On Thu, Apr 9, 2009 at 3:57 PM, Yunior Armando Hernandez Andrade yahernan...@estudiantes.uci.cu wrote: I think Trac should support project planning as an internal functionality, not just an external plug-in... although all options within the functionality should be able to be disabled in the Admin page in case project does not require it. -1 ... Trac offers a minimalistic approach to PM ... so ... About that I think you are all missing some things, there are two concepts within Project planning: 1- Resource Planning, and 2- Resource Tracking. Understand Resource as time, workers, spendable objects (as paper, ink, etc) and long life objects(as hammers, computers, etc)... Resource Planning aims to set tasks (macro-tasks at beginning, that will most likely be composed of other tasks as the project advances), task dependency (four dependency types), estimated task's start and duration time, estimated milestone dates, set each worker's working time and dates, assign workers to tasks, assign time to objects that require it, assign objects to tasks and/or to workers, and so but all that before project starts the hard working. Now, Resource Tracking aims to set task's REAL start and end date, moving subsequent task's start and end dates for next tasks at user wish or simply leaving empty time when wanted, reassign workers and objects to tasks, reassign worker's working time and then reschedule the whole subsequent tasks according to that, rearrange task's dependencies TimeAndEstimation plugin solves SOME of the features in Resource Tracking, MasterTickets almost solves 2 dependency types, etc... but no plugin solves everything needed en project planning. Perhaps all that is true ... however IMHO that indicates that few people have decided to implement all those things, so *MAYBE* its not as mandatory as it seems . -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Se retira el BDFL ... ¿El fin de Python 3k? - http://feedproxy.google.com/~r/simelo-es/~3/HpncxTKfB1c/se-retira-el-bdfl-el-fin-de-python-3k_02.html --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: svn changeset as Comments
Have a look at the post-commit hook. It can also be used to move the ticket along in the workflow, e.g. assign it to a tester after a fix is committed. Ted On Thu, Apr 9, 2009 at 3:41 PM, Sandeep Chayapathi csand...@gmail.comwrote: Hi, Im looking for a way to push the svn changeset (with commit log as the body) as a ticket comment, so that I can see the actual comments on the ticket and also the commit logs. I have looked at the default plugins and couldn't find a way to do this. Any help in this is much appreciated. -- Sandeep -- + - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Requirements for a new and improved Gantt plugin
Yunior Armando Hernandez Andrade wrote: I think Trac should support project planning as an internal functionality, not just an external plug-in... although all options within the functionality should be able to be disabled in the Admin page in case project does not require I admit to being on the fence about this. Properly done, bits of add-in functionality are more maintainable, more approachable, lower overhead, etc. (And more easily developed by a distributed community, I think.) I think of this as the UNIX tools model vs. the 'Windows monolithic blob model. BUT, this is how Eclipse is built and I can't get Eclipse installed with the plugins I need either one at a time or from a pre-built bundle. About that I think you are all missing some things, there are two concepts within Project planning: 1- Resource Planning, and 2- Resource Tracking. Understand Resource as time, workers, spendable objects (as paper, ink, etc) and long life objects(as hammers, computers, etc)... Yes, I see that. But if you're a professional project planner working on the mission to Mars, you're not going to use Trac. There are industrical-strength tools for that. I have 5 developers on my team. We're in a larger group of a dozen engineers. We have 10-15 active projects at once. That's too big to manage intuitively but, I think, too small for all the bells and whistles of resource planning to be necessary. I would not want to give up the information I'd get from a quick-and-dirty Gantt because we are trying to develop One Module that tracks paper clips as well as hours. Resource Planning aims to set tasks (macro-tasks at beginning, that will most likely be composed of other tasks as the project advances), task dependency (four dependency types), estimated task's start and duration time, Maybe ALAP is just ingrained into my workflow and organization but to me start dates are irrelevant. I work backwards from tasks in multiple milestones trying to answer the question, What should I be working on today? (for myself and for my group). ... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Dynamic pull-down population
How would something like this work with queries/reports? That's the main issue I haven't been able to resolve in trying to develop this sort of functionality. The simple answer would be to store the computed value of the field in Trac's DB, but how would it know when to update the value? There are two answers that I have been thinking about, neither one of which I'm fully satisfied with: How about defining several default policies for cache invalidation (such as those listed below), and then allow plugins that define computed fields to provide (via another interface?) their own policy own when to recompute the field? Ted 1. The more robust answer (though maybe still not robust enough): Whenever a /query or /report URL is hit, compute all of the computed fields, as well as doing this every time a /ticket URL is hit. The values are stored in the the Trac DB, specifically inside the ticket-custom table. This would be horribly slow for any sizable number of tickets. 2. The less robust answer: Only do this when individual /ticket URLs are hit. The /query or /reports get cached values. 2. is probably required, at least for my use-cases. You could imagine doing something more intelligent too: * caching fields every N minutes, e.g. with a cron job (if there's not a pluggable cron plugin -- I thought there was but have since been unable to find it -- it would be easy to write). * For /queries or /reports, filter by other criteria to get back the desired ticket set, then compute the computed fields for the remaining tickets and doing additional filtering by these computed values. * For each computed field, cache them on certain events. For instance, some might only need to be cached when the ticket is updated (method 2. above). Others might need to be updated on repository commits. Etc. * Some combination of the above. I admit there's no easy answer for the general case. The event-trigger criterion appeals to me the most, but its easy to see times when it wouldn't work. For instance, if a field requires data from an external service, you won't know when this data will be updated in general. Still, I'm encouraged to try to get something working :) Jeff -- + - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: svn changeset as Comments
On Apr 9, 2:41 pm, Sandeep Chayapathi csand...@gmail.com wrote: Hi, Im looking for a way to push the svn changeset (with commit log as the body) as a ticket comment, so that I can see the actual comments on the ticket and also the commit logs. I have looked at the default plugins and couldn't find a way to do this. Any help in this is much appreciated. -- Sandeep See http://trac.edgewall.org/wiki/TracInstall#AutomaticreferencetotheSVNchangesetsinTractickets - jevans --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Email Notification
On Apr 9, 4:34 am, sunny063 sunny...@googlemail.com wrote: Hi all, I got a problem sending email notifications. When a new ticket is added it takes about 30 seconds to complete this when notification is enabled, also no notifications are send. First our admin told me that smtp-traffic was blocked on the machine that hosts trac, since we wanted notifications enabled he unblocked smtp-traffic. In the meantime I tried a plugin for notifications (AnnouncerPlugin). The logfile tells me: ... 2009-04-08 17:39:30,712 Trac[email_distributor] DEBUG: EmailDistributor has found the following formats capable of handling 'email' of 'ticket': text/html, text/plain 2009-04-08 17:39:30,714 Trac[email_distributor] DEBUG: EmailDistributor was unable to find an address for: all (authenticated) ... Is it possible that all users have enter a valid email-adress? Also I do not want to send a notification to all but I couldn't figure our how to prevent this action. Appreciate your help! Perhaps a config error? Is your admin able to help debug your setup? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Best way to track time spent on tickets?
Sure total hours is fine, but the interface is pretty limited IMO. Thanks for your response. On Apr 9, 4:45 pm, yoheeb yoh...@gmail.com wrote: On Apr 7, 5:21 am, sassers...@sasserstyl.com bjmas...@googlemail.com wrote: I have installed the timing and estimation plugin and the work log plugins - neither of which is entirely satisfactory. Are there any alternatives to help me reduce the time it takes to generate invoices? Total hours is not sufficient to generate an invoice? I like to export a query with total hours in it, for a given milestone to csv, then I hit the Sum button in excel for that column. that said, it's just a field in an sql db, so you could extract it to some other custom tool againts the db, or via xmlrpc. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Best way to track time spent on tickets?
Thanks - I'll try this plugin. On Apr 9, 6:16 pm, Ethan Jucovy ethan.juc...@gmail.com wrote: Have you tried outhttp://trac-hacks.org/wiki/TracHoursPlugin? In terms of time-based reports, it provides views for hours worked on any ticket (/myproject/hours/4 -- time logged on /ticket/4) as well as a project-wide view based on trac's Custom Query which lets you see the hours worked and estimated for each ticket in your query -- which can contain all standard custom query filters as well as date ranges. On Tue, Apr 7, 2009 at 6:21 AM, sassers...@sasserstyl.com bjmas...@googlemail.com wrote: I have installed the timing and estimation plugin and the work log plugins - neither of which is entirely satisfactory. Are there any alternatives to help me reduce the time it takes to generate invoices? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: svn changeset as Comments
fantastic, this is what I was looking for. I would have re-created the wheel and written my own post-commit hook, but this one solves it neatly. Thanks. -- Sandeep On Fri, Apr 10, 2009 at 9:11 AM, jevans jevans...@gmail.com wrote: On Apr 9, 2:41 pm, Sandeep Chayapathi csand...@gmail.com wrote: Hi, Im looking for a way to push the svn changeset (with commit log as the body) as a ticket comment, so that I can see the actual comments on the ticket and also the commit logs. I have looked at the default plugins and couldn't find a way to do this. Any help in this is much appreciated. -- Sandeep See http://trac.edgewall.org/wiki/TracInstall#AutomaticreferencetotheSVNchangesetsinTractickets - jevans --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Dynamic pull-down population
On Fri, Apr 10, 2009 at 10:29:33AM -0500, David Champion wrote: * On 10 Apr 2009, Jeff Hammel wrote: How would something like this work with queries/reports? That's the main issue I haven't been able to resolve in trying to develop this sort of functionality. The simple answer would be to store the computed value of the field in Trac's DB, but how would it know when to update the value? There are two answers that I have been thinking about, neither one of which I'm fully satisfied with: I've taken a look at this kind of thing too, and my gut tells me that in these two proposals (as responses to this other poster's question) you may be attacking two separate but related problems at once. 1. There is a need for a provider interface for custom fields and their possible values -- an extension point to supplant [ticket-custom] in the config file. I agree: http://trac.openplans.org/trac/ticket/29 2. There is need for an extension which implements this extension point and may do roughly what you're talking about. I agree here too: http://trac.openplans.org/trac/ticket/28 I really need #1, but I don't need #2 at all. For my project I would deliver custom field definitions from an external source, and it wouldn't matter to me what values currently exist in the db, nor would I want to alter my db to store any of this information separate from the custom field values themselves. In my opinion, these are separate projects. Yes. 2. will build on 1. To me the best approach to #1 is a patch to trac.core. Sure, but I can write a plugin now instead of waiting for the patch to be in some Trac release. The patch should be written, but personally, I use plugins vs. patches whenever possible I don't see the value of implementing as an ITemplateStreamFilter except that you can currently do it as a plugin... but filtering the stream seems like a last resort when the basic functionality is already present. Yeah, not needed for 1., probably needed for 2. (or maybe IRequestFilter). However there's no existing extension point that you can tap into to offer the custom field metadata. The only custom field metadata source is currently hard-coded as [ticket-custom]. Yeah, I agree this is undesirable. If #1 is implemented as a new extension point in the spot where [ticket-custom] is now, then #2 is easily a separate plugin implementing that interface. Likewise, [ticket-custom] can be reimplemented as a plugin using that interface. Yeah, though I see no reason to redo [ticket-custom]. Its perfectly reasonable for people to put fields there, at least in the forseeable future (I can only think to maybe Trac 0.12 in my mindand barely at that) There are good examples of caching the field information already in trac.core -- [ticket-custom] itself illustrates this. None of these modifies the db itself, nor would it seem to benefit from doing so. Jeff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Requirements for a new and improved Gantt plugin
Cris Lang wrote Yes, I see that. But if you're a professional project planner working on the mission to Mars, you're not going to use Trac. Why not Trac is customizable, easy to learn, robust and more important: Trac is free software. In the name of all heavens, Trac is great! And I don't say it for myself, 96% of the Cubans that work in some kind of project says it. Why not to use it in my mission to mars project??? Answer: Lacks functionality. From my point of view Trac can easily become the best project management tool ever IF we all think what to do to accomplish that and stop been so conformist. The idea of this being great and not to need new things just because it works for what I do is not the best way to make it. Maybe ALAP is just ingrained into my workflow and organization but to me start dates are irrelevant. I work backwards from tasks in multiple milestones trying to answer the question, What should I be working on today? (for myself and for my group). Well you'll have to agree with me that then YOU ARE planning, just not from the right approach. You plan everyday what you're going to do that day, so you start date is...(background suspense music)... TODAY! My people, planning is the key to controlled progress, just that we all have not enough team work culture to plan everything in advance doesn't mean your project don't need it or you don't need it. Anyway, maybe is not a priority for you all. So I'll keep learning python so that I could do it myself. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Requirements for a new and improved Gantt plugin
On Fri, Apr 10, 2009 at 12:35 PM, Yunior Armando Hernandez Andrade yahernan...@estudiantes.uci.cu wrote: Cris Lang wrote Oh my ! What t(he)ll ! I've a cloned out there ! ... Is this a chimera ? How many heads ? Oh my god ! What plugin did I install to get that done ? Please tell me ... Did Emperor Vader send it to conquer the Earth ? -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Se retira el BDFL ... ¿El fin de Python 3k? - http://feedproxy.google.com/~r/simelo-es/~3/HpncxTKfB1c/se-retira-el-bdfl-el-fin-de-python-3k_02.html --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Requirements for a new and improved Gantt plugin
On Apr 9, 9:01 am, Chris Nelson chr...@sixnetio.com wrote: To effectively display project progress, tickets must have estimated and actual times as in the TimingAndEstimation plugin. Is this sched vs execution (plan vs real progress ;) time? My bias is for the way we use it here: actual is how much time you've put in. Estimate is how long it's expected to take. When we accept a ticket, we put in an initial estimate. If we find out that the task is much more or less complex than originally believed, we revise the estimate. Time remaining is always estimate-actual. However, since this seems to be a matter of contention, I think I'd take Yogi Barra's advice (When you get to a fork in the road, take it.) and add a configuration option to specify whether remaining time is in the DB or must be computed. Personally, I'd like to see 3 values - the original estimate, the actual work time spent, and the remaining estimate. During development, I am most interested in the current estimated time remaining. After completion it can be useful to compare the time it actually took with the initial estimate. - jevans --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
