On Nov 21, 4:05 am, "Christopher Taylor" <[EMAIL PROTECTED]> wrote:
> > > unfortunately, I had to write this into report.py. I don't suppose
> > ya'll
> > > would like this patch? I could aldd a few other things like $THISWEEK,
> > > $THISMONTH but we dont' really have a need for that.
>
> > I'm curious as to what you use these variables for in the reports
> > you've done? The TNE manager passes in dynamic variables into the
> > reports so it should be easy enough to modify it to pass in these
> > specific values if they are genuinely useful (e.g. calculate them in
> > real time when generating the report links - it should just be a small
> > change to linkify.js).
>
> well i added chargenumber as a custom ticket field and a report that reports
> how many hours the current user charged to a given charge number that day
> ... this helps them fill out daily time cards.... it was a lot more
> convienient than having the developers type in the date in the mgt tab each
> day ... there's some more work that needs to be done ... specifically I need
> to tabulate each charge number individually...
I think you'll be pleasently surprised if you use two of my plugins in
combination with T&E:
ClientsPlugin: http://www.trac-hacks.org/wiki/ClientsPlugin
This adds "client" and "clientrate" custom fields and the ability to
define a list of clients in the Admin area. Each client can also have
a default "rate" associated with them (e.g. hourly $£EURO value) which
is autopopulated to the ticket when you select a client (although it
can be overridden on a ticket by ticket basis). Without knowing how
you work, it sounds like this is similar to your "charge number". It
also adds some custom reports that are added to the T&E management
page to allow the hours summary to be grouped by client and to
multiply the hours by the ticket's rate to make for easy billing
reports.
The second plugin (and probably the most useful) is:
WorkLogPlugin: http://www.trac-hacks.org/wiki/WorkLogPlugin
It adds a "start work" button to each ticket that allows you to easily
track time you spend on a ticket. It optionally integrates with T&E to
automatically add the hours to the ticket when you stop work and
allows you to allocate a "rounding value" (e.g. round to the nearest
15 minutes).
These three plugins are how we track time, and billing in our office.
Hopefully they can help you too!
I will say tho' that I'm only developing them for 0.11 now. The 0.10
version of Clients plugin is rubbish and needed a patch to trac which
was a bit ugly. The new one is much better. Worklog for 0.10 works
pretty much OK, but 0.11 version has a few more features and is the
one I'm actively developing. The Wiki pages for both are lacking and
need updating/screenshots etc.
> as for putting these in the linkify.js, I suppose that would work and it
> would be a lot easier from a maintenance perspective .... unfortunately, I
> need this report as easy as possible for the other developers to use so
> they'll use it to build their timecards...
Using the clients plugin you'll get reports added automatically to the
the T&E management page which is I think what you're after :) I've
also got some changes to T&E that adds a calendar widget to the
Management report which would make entering in the date ranges that
interest you very quick and easy (e.g. one click). You could also
create your own "plugin" that just added new reports using the
reportmanager.py file (just copy it from the client plugins svn area).
This file is designed to be a common file that several plugins can use
(copy around) to make adding custom reports to plugins like T&E easy.
Longer term we aim to create a manager in the admin area that would
allow you to add your own reports to the list in the management
screen.
Putting it in linkify is the correct approach here if the DB's date/
time functions are not sufficient as Alec has suggested. There doesn't
need to be a patch to track.
Also fully upper case variables denote an external variable. If you
were going to provide these variables the way you have they would have
to be lower case to avoid clashing with user variables.
HTHs
Col
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" 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-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
