[Trac] slow /report page
Hi, How can I make that page [mytrac]/report faster? "New ticket" in the main menu leads to page /report and it's very slow in our Trac 1.0.4 system now since we have added a lot of reports over the years. It seems opening that page immediately pre-renders all reports which takes several seconds, although I just want to click of one of the reports in the end. Is it just my misconfiguration or is/was it a known problem? Thanks in advance, -- Falk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: UpcomingMilestonesChart and quotes
Hi Roger, please provide an own patch, the code is super easy. The plugin is good enough for our own environment but I shared it on trac-hacks but I don't plan to further investigate... CU, Falk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Site maintenance
Hi, Generally a good idea, but why that effort? What is it worth for? Your spent time should have a good cost-value ratio. :-) CU, F@lk Am Mittwoch, 16. Dezember 2015 03:06:00 UTC+1 schrieb figaro: > I am looking for feedback on the following proposal for the Trac website. > The proposal regards a list of links to pages that require cleanup. The > resulting page could be integrated in HowToContribute or TracDev/ToDo#Wiki > > > Site maintenance > > The following is a list of pages that help in maintaining the Trac site. > Maintaining the site involves routine cleanup of wiki pages, so that the > site's content remains consistent and fresh. The pages that need to be > maintained are not marked as 'deprecated' or 'pending-deletion'. The same > site maintenance guidelines and links can be added to your Trac > installation. > > Dusty pages: pages which have not been edited in at least 5 years usually > require a cleanup or can be marked for deletion. See RecentChanges. > > Pages with obsolete macros: there are some obsolete macros still > circulating in the wiki, such as TagIt[[()]], and they need to be removed > from the page. > > Images: a list of all images on the Trac installation is useful for the > following purposes: > - if a list of the wiki pages or ticket pages that they are used in is > provided also, then obsolete (ie unused) or duplicate images can be more > easily detected. > - if thumbnails are automatically generated also, then detection of > irrelevant images: someone may have uploaded an image in the past that is > irrelevent to the use or development of Trac. > - jpgs may have been used, where png or svg is the norm. > > Attachments: a list of all attachments on the Trac installation is useful > for the following purposes: > - if a list of the wiki pages or ticket pages that they are used in is > provided also, then obsolete (ie unused) or duplicate attachments can be > more easily detected. > - someone may have uploaded an attachment in the past that is irrelevant > to the use or development of Trac. > > Acronyms: misused or accidental acronyms where spelling them out would > make the text clearer: from db to database, from regex to regular > expression, from " to ". > > Short pages: pages with little text are usually the result of a test or > have been abandoned and are therefore candidates for deletion. > > Dead links: dead links in the wiki show up as grey links if they are > internal links and need to be corrected or removed. Dead links to external > sites have no special highlighting, but still require correction or removal. > > Protected pages: pages that are read-only may need to have their status > reviewed. > > Pages without table of contents: pages should have either > `[[TracGuideToc]]` or `[[PageOutline(2-5,Contents,pullout)]]` in them for > navigational purposes. > > Undocumented Python objects: functions and classes in Python that do not > have any code comments. > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Roadmap page results in error whith SimpleMultiProject plugin and Trac 1.0
The error should be fixed now with trac-hacks revision 15049 <https://trac-hacks.org/changeset/15049>. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Roadmap page results in error whith SimpleMultiProject plugin and Trac 1.0
Yes, please, add: from trac.util.text import to_unicode I haven't the development environment here currently, so I just think out loud. CU, falkb Am Montag, 9. November 2015 14:26:00 UTC+1 schrieb oneman: > > So, I've got it to execute the updated egg now. That results in > 'NameError: global name 'to_unicode' is not defined'. Should I add an > import? > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Roadmap page results in error whith SimpleMultiProject plugin and Trac 1.0
Hi! See my comment in https://trac-hacks.org/ticket/12568#comment:4 CU, falkb -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: MasterTicketsPlugin and SimpleMultiProject, approaches for large projects
Am Montag, 1. Juni 2015 13:40:32 UTC+2 schrieb Mo: > You use MasterTicketsPlugin and SubticketsPlugin at the same time? They don't seem to be compatible. Adding SubticketsPlugin, a ticket with already "blocked by" and "blocking" from the MasterTicketsPlugin doesn't change anything in the Subtickets section. They are compatible. SubticketsPlugin gives you the parent<->child hierarchy feature, while MasterTicketsPlugin gives you a dependency relationship I use usually between siblings. > That TracJsGanttPlugin is only for adding to Wikis? There is no menu item with the Gantt charts per milestone? Just add the Gantt chart to the milestone description and it'll come up with every milestone on the Roadmap page. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: MasterTicketsPlugin and SimpleMultiProject, approaches for large projects
Am Montag, 1. Juni 2015 12:47:04 UTC+2 schrieb Mo: > > > First question is if tracking tickets is a useful approach anyway? > > Not sure what you mean with "tracking" > > With "Tracking tickets" I mean tickets only used to group other tickets. Ah, you don't mean "... to track tickets is a useful approach..." but "... tracking-tickets are a useful approach...", right? I usually also group tickets (with a new ticket type for grouping), but I use MasterTicketsPlugin and SubticketsPlugin as suggested here: http://trac.edgewall.org/wiki/PluginList#ProjectTimeManagementTicketSystemExtensions . The hierarchy has often depth = 3, it's very useful for displaying with Gantt charts when there are many tickets in a milestone or project, and I display the whole stuff with *TracJsGanttPlugin* <http://trac-hacks.org/intertrac/TracJsGanttPlugin> where I can setup the openLevel parameter. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: MasterTicketsPlugin and SimpleMultiProject, approaches for large projects
Am Montag, 1. Juni 2015 11:54:45 UTC+2 schrieb Mo: > First question is if tracking tickets is a useful approach anyway? Not sure what you mean with "tracking" > ...the dependencies to tracking tickets are not useful either... Why? What do you mean? > Any suggestions? Suggestions for what? Sorry, your posting is completely not clear to me. :) CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: SimpleMultiProject and project.options
Am Dienstag, 12. Mai 2015 14:18:01 UTC+2 schrieb Mo: > Hm, interesting. Disabling that option still provides the drop down list > with new projects and also accepts these. Some time ago it was required to > have that option line in the configuration to make it work. Seems to work > now without the line. > > Yes, this is my experience, too. I was surprised when I once saw it works without also. Though I cannot tell if it was a problem in earlier days, or if it still has drawbacks. We must keep an eye on it... CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: SimpleMultiProject and project.options
This has something to do with the behaviour of the combobox. At present it needs options set in trac.ini. I don't have a solution at the moment. Ideas appreciated. Or what exactly happens if you remove the whole line with "project.options"? Am Dienstag, 12. Mai 2015 12:02:02 UTC+2 schrieb Mo: > > Hi, I'm using SimpleMultiProject for some time now to have another level > of Component without managing several trac instances. > > However adding a new project is offering that new project in the drop down > list of New TIcket, but fails with "Unknown project" until I add the new > project to > [ticket-custom] > project.options = Internal:Trac|Project_A|Project_B|Project_C > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac 1.0 + Bitten + mySql Lite Support
Am Donnerstag, 12. März 2015 17:24:27 UTC+1 schrieb tol...@gmail.com: > Does that affect the results that are stored in trac's database though? If I wanted to look at the build results from revision 5000 and now I'm on revision 1, but set the "First revision" to 9800, wouldn't everything before 9800 be deleted? > Maybe there's a way bitten can be changed to only check up to the last 200 revisions when a slave request is trying to see if there are any pending builds. I don't know. We just use Bitten as check if commits went well, and the history doesn't matter, so I don't know if setting the first revision invalidates older builds, but I know the bitten build log files (under /log/bitten) aren't deleted on the server. Maybe "[x] Build all revisions" in Admin/Builds/MasterSettings is also a choice for you. Anyway it may lead you to the piece of code you need to hack in the Bitten server sources to get the "minus 200"-hack you want. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Trac 1.0 + Bitten + mySql Lite Support
Hi, Am Mittwoch, 11. März 2015 18:56:28 UTC+1 schrieb Tom Luiz: > > > Any idea why Bitten is slowing things down a lot? I know we have a patch > that was applied to add some desired functionality to Bitten, like > keep-alive communication, network timeout retries, etc. > I also use Bitten and know about the performance brake it is, but I have a little trick that speeds Trac up again: You simply must set the "First revision" of the "Repository mapping" in the build configurations to a newer one from time to time. I noticed things start to sensibly slow down if the "First revision" is about current revision minus 200. I can't quite remember but I think someone said on the Bitten mailing-list the reason is that a Bitten slave request iterates down the SVN builds from current to first revision for checking if there's something to do. If you never have adapted your first revision of the Bitten Build Configuration, you may have thousands of revisions that each Bitten slaves periodically checks, and that may be one of the reasons for the 100% CPU load. Anyway things speed up here when I adapt that Bitten setting... CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Status of AnnouncerPlugin
I use it with trunk version [12503] without seeing instability over all the months. Trac is 1.0.1 at the moment. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: mainnav items for lot of plugins
Hi, have you seen http://trac.edgewall.org/wiki/TracNavigation#nav-order ? CU, F@lk Am Montag, 9. Februar 2015 12:08:59 UTC+1 schrieb Mo: > Hi, > > I like to sort the default mainnav list. > As for most of the plugins I don't know what the names of the items are. > Is there any plugin offering a generic sort list of mainnav? Or do I need > to fetch all items from the plugin sources? > > I guess this means grepping all webui.py in the *.egg for "yield 'mainnav' > Right? > > Best regards. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Customize Trac "Available Projects" for User
Hi, I have a short check and at least you can switch the whole project list page off by not giving PROJECT_SETTINGS_VIEW permission to users who aint administrators. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Customize Trac "Available Projects" for User
Hi Aikido Guy, you should always mention what plugin your posting refer here. You're talking about SimpleMultiProjectPlugin, and you've wrote a comment on trac-hacks for it as I noticed in http://trac-hacks.org/ticket/11367#comment:39 , already. At present I don't have much time for Trac development, but your idea is reasonable and likely quite easy to implement. Probably, I find the time during December when I have holidays. CU, F@lk P.S.: Look at the SVN commits of TH:#11367, there you can see how it must be done, basically a check is to insert like this: if self._SmpModel.is_not_in_restricted_users(username, project_info): return False -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Can Trac Hidden Project List?
Hi! In case you use SimpleMultiProjectPlugin (hosted on trac-hacks.org): Go to Admin page => Manage Projects => Projects => select your project => fill out the field "restricted to users" with a comma-separated list of user names CU, F@lk Am Mittwoch, 12. November 2014 10:35:45 UTC+1 schrieb 柯餅乾: > > Hello everyone, > I'm a new user for Trac. > I have a problem that how can I make a distinction for different user to > display different project according to their different permission. > And how to hidden the project that the user doesn't have the permission on > those. > > > thank. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Help configuring TRAC to better un/assign projects.
F@lk wrote: > (2.) Just use http://trac-hacks.org/wiki/SimpleMultiProjectPlugin to have all your company-projects in one trac database and environment. ...snip... > permission_policies = ProjectTicketsPolicy This allows to restrict projects to certain users, a feature of the plugin. Can be configured on its Admin page via webinterface. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: Help configuring TRAC to better un/assign projects.
Hi, (1.) Install a consistent all-in-one-package like Bitnami Trac to prevent incompatibility trouble with Apache, Python, SVN, Trac and so on... this will give you a very fast installation start. (2.) Just use http://trac-hacks.org/wiki/SimpleMultiProjectPlugin to have all your company-projects in one trac database and environment. (3.) Configure your finegrained SVN permissions via Apache webserver config file "httpd.conf" and its -approach, e.g. like this snipped in apache/conf/httpd.conf: ... DAV svn ... AuthzSVNAccessFile "C:/repos/yourRepo.conf" - and file "yourRepo.conf" will look like this: [groups] group1 = user1, user2, user4 ... [yourRepo:/] @group1 = rw user3 = r [yourRepo:/branches/subdir/foo2] user5 = rw ... (4.) The permission thing is configured in conf/trac.ini and is highly configurable via AuthzPolicy permission approach: ... [authz_policy] authz_file = conf/authzpolicy.conf [components] tracopt.perm.authz_policy.authzpolicy = enabled [trac] permission_policies = ProjectTicketsPolicy, AuthzPolicy, InternalTicketsPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy ... and in conf/authzpolicy.conf for example: [groups] group1 = user1, user2, user3 group2 = user1, user4, user5 [wiki:WikiStart] @group1 = WIKI_ADMIN * = WIKI_VIEW This is a small example. Searching the docs should enlight you a bit more. Hope that helps as a start, CU, F@lk Richard Smith wrote: > Hello everyone! I am currently so lost with TRAC. I am relatively new at my company and they are wanting me to configure their TRAC which I have never used in my life. I am needing to make it easier for my boss to assign and unassign people from 30 different projects. He would also like to setup up presets like devs or admin with different privleges and then be able to assign them to a project. I have downloaded Python 2.7 on my machine and currently have TRAC's authz_policy.py Also after I do get this file configured how would I implement it? I have had little interaction with scripting, but I have a decent handle on it. If you can help I would greatly appreciate it. Thank you guys! > -Richard S. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Question about next Trac 1.0.2 release
Hi, Rjollos wrote: > Steffen captured the essence of it. I will say that, that we aren't holding back just to get another ticket or two finished. It really comes down to the long-time Trac developers finding time to show us new Trac developers have to prepare the release. However, everyone on the project volunteers their time, and they currently have none to commit. how many time would it take when the long-time Trac developers show you how to prepare a release? Sometimes I can see them in the t.e.o. timeline working at tickets although this one is actually a blocker. Sorry for bugging. ;) CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: Consistent setup of TimingAndEstimationPlugin, EstimationToolsPlugin and TracJsGanttPlugin, help needed
Am Freitag, 7. Februar 2014 13:28:49 UTC+1 schrieb F@lk:
You are right, I forgot, once I patched T&E plugin with this little one:
>
> Index:
> branches/trac0.12-Permissions/timingandestimationplugin/htdocs/query.js
> ===
> ---
> branches/trac0.12-Permissions/timingandestimationplugin/htdocs/query.js
> (revision 13336)
> +++
> branches/trac0.12-Permissions/timingandestimationplugin/htdocs/query.js
> (working copy)
> @@ -1,6 +1,6 @@
> $(document).ready(function(){
>// Fields we will total
> - var columns = ['totalhours','estimatedhours'];
> + var columns = ['totalhours','estimatedhours', 'remaininghours'];
>var tbodies = $('table.listing.tickets tbody');
>
>tbodies.each(function(idx, tbody){
>
I wished these 3 custom ticket fields would be part of the regular ticket
DB table (as well as 'project' should be part of the native Trac database).
Then we would have a standard definition plugins could consistently use.
And all those SQL queries in the plugins would be much easier than to
search in the ticket_custom and ticket_change tables which is much more
expensive at run time, and also more complicated to implement.
But, unfortunately, project management support is still thought as addon
and not part of the core system.
CU, F@lk
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Trac] Re: Consistent setup of TimingAndEstimationPlugin, EstimationToolsPlugin and TracJsGanttPlugin, help needed
Hi,
Am Freitag, 7. Februar 2014 11:39:36 UTC+1 schrieb Kristian Nørgaard:
>
>
> regarding a):
> You are right. I mixed the custom query up with the reports that comes
> with TimingAndEstimationPlugin. And these reports I can fix myself.
> But how do you get the "remainingtime" to sum up in custom query?
>
You are right, I forgot, once I patched T&E plugin with this little one:
Index:
branches/trac0.12-Permissions/timingandestimationplugin/htdocs/query.js
===
---
branches/trac0.12-Permissions/timingandestimationplugin/htdocs/query.js
(revision 13336)
+++
branches/trac0.12-Permissions/timingandestimationplugin/htdocs/query.js
(working copy)
@@ -1,6 +1,6 @@
$(document).ready(function(){
// Fields we will total
- var columns = ['totalhours','estimatedhours'];
+ var columns = ['totalhours','estimatedhours', 'remaininghours'];
var tbodies = $('table.listing.tickets tbody');
tbodies.each(function(idx, tbody){
>
> regarding b):
> If I understand your solution correctly, then the ticket bar length stays
> fixed (as you do not change "estimatedhours") and the "remainingtime" is
> only indicated by the way that tickets are scheduled after one another.
> So if the "remaininghours" are larger than "estimatedhours - workedhours"
> you will have a gap in between ticket bars?
>
yep, I've seen that behaviour.
> And if the "remaininghours" are smaller than "estimatedhours -
> workedhours" you will have tickets bars to overlap?
>
yep, in the end of a project they appear much pushed together. If you're
running after the release date, the ressource will be on the left side of
the current (blue) week, otherwise on the right side.
>
> So you will only see the remaining hours indicated if another ticket is
> following, right?
>
Yes. I wished there was a little vertical line in the ticket bar displaying
the start of the rest hours (calculated back from the ticket end point).
> Also I am not sure that I find the original "estimatedhours" relevant in
> the Gantt chart.
>
I find it useful to see what the biggest amounts of work were.
>
> I was imagining a more simple solution: that the ticket bar was displaying
> "remaininghours + workedhours" in stead of "estimatedhours".
> And if I am patching the TracJsGanttPlugin anyway, I might as well create
> my own hack...
>
A start point might be to use the source code of
http://sourceforge.net/projects/projectlibre/ because they have implemented
a correctly working Gantt chart with all bells and whistles and correctly
working ressource leveling agorithms, also displaying the original plan and
the current state in one chart. I would also be very interested in such
clone.
>
> I just always worry a bit about a framework, if I quite early in the
> customization needs to create my own patches...
>
It's definitely not perfect, but with little tweaks one can get 90%
working. Think twice if the big effort for the 10% rest is the result
worth.
CU, F@lk
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-users+unsubscr...@googlegroups.com.
To post to this group, send email to trac-users@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.
[Trac] Re: Consistent setup of TimingAndEstimationPlugin, EstimationToolsPlugin and TracJsGanttPlugin, help needed
Hi, Am Donnerstag, 6. Februar 2014 10:22:38 UTC+1 schrieb Kristian Nørgaard: 3. Interpret "estimatedhours" as a fixed field, in the meaning of "INITIAL > estimated total time". > I use this approach. I use 3 additional custom fields with the following meaning: 1. estimatedhours.label = originally planned time 2. remaininghours.label = currently estimated rest time 3. totalhours.label = sum of worked time > This doesn't make much sense for the various graphs unless you add another > custom field "remaininghours" to mean the "recently estimated remaining > time". > > But this solution does still not provide consistent interpretation: > > a) For custom queries TimingAndEstimationPlugin still sums up > "estimatedhours" - "totalhours", so this number will often be different > from the field "remainingtime" (though they claim to give you the same > information) > Not sure what you mean. Where does it sum up that difference? I just know the sum up in the ticket query result table but each column has it's own sum there, and there's no subtraction. > b) Also TracJsGanttPlugin can not show the actual situation since no > single field provides the "currently estimated total time" which would be > the input it needs for "fields.estimate" > I use a patch to TracJsGanttPlugin I've posted in https://trac-hacks.org/ticket/11549 now. The chart is computed based on the remaininghours, but the ticket bar length is equal to the estimatedhours. The inner black bar is totalhours against estimatedhours in percent. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Trac] Re: How to use macros e.g. from EstimationToolsPlugin?
Hi, Am Montag, 3. Februar 2014 17:35:28 UTC+1 schrieb Kristian Nørgaard: > > Seems that at least RoadmapHoursPlugin does not have the configuration > options that allows using "remaininghours" in stead of "estimatedhours". > Am I on a path that violates some of the plugins dependencies? > Well, sorry, I don't use RoadmapHoursPlugin. No idea. Do you actually know this plugin set suggestion?: http://trac.edgewall.org/wiki/PluginList#ProjectTimeManagementTicketSystemExtensions CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Trac] Re: How to use macros e.g. from EstimationToolsPlugin?
Hi, Am Montag, 3. Februar 2014 17:17:55 UTC+1 schrieb Kristian Nørgaard: > > Thanks, good practice is exactly what I am looking for, examples of what > will work together and what won't. > If I end up documenting the setup I have, where would be a good place to > publish this? > No idea. > > I am testing on a copy of our production setup, so I can do all the > experiments I want! > > Ok, so now I have the four custom fields as you list them: > totalhours, estimatedhours, remaininghours, hours > > And apart from T&E plugin updating the totalhours, I guess there is no > automatic interaction between these fields? > No, there isn't automatic interaction. It's up to you how to deal with the values in the fields. ...snip... > > It seems to work in my first short tests. > Is this a "good practice" setup? > Yes, looks good. > > And your policy is then: > * estimatedhours are only changed up front, before the ticket work is > starting. > * remaininghours are updated as you go on > Yep. I also add the worked hours manually from time to time, actually once in a week whenever I correct the remaininghours value. That's enough for my purposes. > > And then hours are added through a post-commit hook? > I don't use the post-commit hook for adding worked hours. Often I add hours after testing which is quite some time after the last commit. We found out, it's enough to add worked hours and correct the remaining hours right before a resource meeting, because then it should be up-to-date. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Trac] Re: How to use macros e.g. from EstimationToolsPlugin?
Hi, Am Montag, 3. Februar 2014 12:00:07 UTC+1 schrieb Kristian Nørgaard: > > Will I have to perform database hacks also, as described in > http://trac-hacks.org/ticket/8681 > ??? > the manual DB tweaking described in #8681 is just necessary in this situation: - firstly, you used only EstimationToolsPlugin with ticket field 'estimatedhours' in the meaning of "recently estimated rest time" - secondly, after a while you wanted to use also TimingAndEstimationPlugin or TracJsGanttPlugin and recognize they use 'estimatedhours' in the meaning of "originally planned time for the ticket" The issue reported in #8681 reports the clash of the meaning of that ticket-field, and suggests how you can overcome the problem. Kristian, the a good practice is to use these 3 ticket fields: [ticket-custom] totalhours = text totalhours.label = sum of worked time totalhours.value = 0 estimatedhours = text estimatedhours.label = originally planned time estimatedhours.value = 8 remaininghours = text remaininghours.label = currently estimated rest time remaininghours.value = 8 For example, estimatedhours could be 120 hours (your plan), and you have 100 totalhours (what you've worked so far), and you still judge 100 remaininghours (currently expected rest time). and T&E plugin also internally needs: hours = text hours.label = adds another time to totalhours hours.value = 0 Then the charts should properly work. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Trac] Re: How to use macros e.g. from EstimationToolsPlugin?
Hi, Am Montag, 3. Februar 2014 10:24:41 UTC+1 schrieb Kristian Nørgaard: > > I like the BurndownChart, but it only shows a drop in hours when a ticket > completes. > You need to set this in trac.ini [estimation-tools] estimation_field = remaininghours Then it counts down the time you estimate as the remaining work. This can highly vary from your originally planned time. Of course, you need to periodically rejudge each ticket for how long you expect the work may still take. My experience is it's enought to go through the project ticket list once in a week. That depends on how fine-granular your plan is, and for how long you schedule your release date. CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
[Trac] Re: How to use macros e.g. from EstimationToolsPlugin?
Hi, Am Sonntag, 2. Februar 2014 21:41:21 UTC+1 schrieb Kristian Nørgaard: > > > I have found out how to display the sum of remaining hours for a > milestone, but only by manually entering a macro in the description field > for the milestone. > Is there any more automatic way of using these macros that I have overseen? > No, there isn't any other way of using it. You can insert it at any place where wiki formatting is possible. > > How are you using them? > 1. description field of milestone 2. description field of version 3. project wiki startpage > Can the macro parameters somehow be dynamically set? > No, you can't. > Share your macros... for which views are you using which macros and how? > [/version/blabla] contains || [[BurndownChart(version=blabla,startdate=2014-01-,enddate=2014-03-,weekends=false,title=,width=500,height=250,label=Rest)]] || [[WorkloadChart(version=blabla,status!=closed,width=400,height=133)]] || [/milestone/blabla] contains || [[BurndownChart(milestone=blabla,startdate=2014-01-,enddate=2014-03-,weekends=false,title=,width=500,height=250,label=Rest)]] || [[WorkloadChart(milestone=blabla,status!=closed,width=400,height=133)]] || [wiki:Foo] contains: [[BurndownChart(project=Foo, startdate=2013-07-,weekends=false,label=Rest)]] [[WorkloadChart(project=Foo)]] CU, F@lk -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
[Trac] Re: time estimation plugins - your recommendations
Hi, I’ve been using that plugin (0.12 with permissions) for a long time now (currently with 1.0.1) and my experience is: - The addition of the 2 ticket fields “estimatedhours”, “hours” and “totalhours” is very useful and works without problems. The permission branch of the plugin allows to limit the field access to certain users which is also very useful. - The adding of worked hours via Ticket input field is very handy. - The integration with TracJsGanttPlugin<http://trac-hacks.org/wiki/TracJsGanttPlugin> and EstimationToolsPlugin <http://trac-hacks.org/wiki/EstimationToolsPlugin>works very well - But the whole thing under main menu item “Time reports” is IMHO not intuitive and also completely not usuable for me because fixed to hard-wired billing-dates one even cannot delete anymore. For instance, I cannot make queries for certain SMPP<http://trac-hacks.org/wiki/SimpleMultiProjectPlugin>projects or simply between two milestones, or between two versions, or between two datetimes I could set per variable parameters to a query. - There is no demo site (although I wished trac-hacks.org has one) - The removal of the plugin is no problem - Hours or days do not matter since the plugin does not give you a unit. It’s up to you how you interpret the numbers. - See http://trac-hacks.org/wiki/TimingAndEstimationPlugin#RecentChangesfor the development activities CU, F@lk > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/groups/opt_out.
