Back end - Reporting

More
14 Aug 2013 23:42 #1367 by brentmin
brentmin created the topic: Back end - Reporting
One BIG feature I would like to see soon is the ability to run, in the Pro version, a report on each collaborative developer on my team with the following criteria:

1. The ability for me to determine whether hours spent are productive (and thereby billable) or non productive.
2. The ability to add up productive hours and non productive hours.

I now have to do this manually for each developer in the back end.

Please would you respond to this reques?

Please Log in or Create an account to join the conversation.

More
14 Aug 2013 23:44 #1368 by admin
admin replied the topic: Re: Back end - Reporting
Hello,

reports are on my endless to-do list :)
Just a question: how do you decide if an hour is productive or not? It should be a sort of "flag" on the recorded activity?

Please Log in or Create an account to join the conversation.

More
14 Aug 2013 23:54 - 14 Aug 2013 23:54 #1369 by brentmin
brentmin replied the topic: Re: Back end - Reporting
We have an interesting setup. I am involved in drug and alcohol rehabilitation taking young failed starters in life, getting them off of substance abuse and then employing them, training them up to develop Joomla sites for our business. So some of the tasks we give them are learning tasks which we do not pay them the same rate for. So they may spend three hours on a task that should only take an hour to do. For this we have an unproductive / training rate. For jobs they are fluent with they get the production rate which is higher. This does not affect what we bill the client, but it does affect what we pay them.

I need to be able to select a project as unproductive and add up the hours and then other projects as productive and add up the hours. We then transfer these totals for the month to the staff member's pay slip which then converts the two to currency and totals it. We then pay them accordingly.

While our situation may seem unique, in reality it is not. Many companies have different rates to hours.

I would even be happy if I was able to select productive hours and just get a total for each staff member on this. The unproductive hours are few so I can single that out.

Does this make sense to you?
Last Edit: 14 Aug 2013 23:54 by brentmin.

Please Log in or Create an account to join the conversation.

More
14 Aug 2013 23:56 - 14 Aug 2013 23:57 #1370 by brentmin
brentmin replied the topic: Re: Back end - Reporting
Yes it can be a flag on the activity if it is unproductive. Then the tally at the bottom of the activity list would not include these. This would work for me. Right now I have to add up the hours with a calculator.
Last Edit: 14 Aug 2013 23:57 by brentmin.

Please Log in or Create an account to join the conversation.

More
15 Aug 2013 00:00 #1371 by admin
admin replied the topic: Re: Back end - Reporting
yep, it does.

I suggest you this approach, tell me if it's ok or not.
I suppose that the skills are generic (ie "Learn to do Task A") and they apply to several customers, right?
If it is, you could create a new project, named "Training in task A" and then track these hours with that project.
Then, when they are really working, you can create a new activity and start tracking it as a "regular" one.

In this way you will know how much hours have been spent on training for "Task A" and at the same time you will have a correct bill for the customer.

Is this a solution for you?
Of course the part of the nice report is missing, but I'll try to add them as soon as I get some time.

Please Log in or Create an account to join the conversation.

More
15 Aug 2013 00:05 #1372 by brentmin
brentmin replied the topic: Re: Back end - Reporting
That could work. But for now it would help to have at the bottom of the Activities screen a total of hours for each of the users when they are selected. We would select user and date search for the period eg. 25 July to 24 August. This could be an easy to add interim measure, don't you think?

Please Log in or Create an account to join the conversation.

Time to create page: 0.258 seconds