search

hicknhack-software / redmine_time_tracker

A time tracker plugin for Redmine
Other
106 stars 32 forks source link

Missing functionality (Feature permission) #179

Closed erakis closed 7 years ago

erakis commented 10 years ago

I don't know if this feature is already exists but could it be possible to allow the user to ONLY start timer on it's assigned issues and PREVENT him to start global timer and stop it without any bookable time result ?

In other word, is there a way that user can ONLY do BOOKABLE time.

Best regards,

jume-dev commented 10 years ago

I don't think this is implemented, but i wonder, why would you need such a feature? Can you me a useful example, why someone would want this?

erakis commented 10 years ago

We have some employees here working on several projects simultaneously. And they are not all programmers or comfortable with computer software. They simply want a kind of simple puch that associate their time to a precise issue ;) In the other hand, the project manager or accounting person want a complete CRM giving details of all time worked to produce report.

PS : By Punch I mean simple as start/stop button above an issue. Exactly what the plugin do actually. But they don't want to edit a day/week big table entries by entries...

Sometimes they have to punch time from an isssue to another one and several times per hour/days. The fact that they can start and stop timer globally can lead to many timelog being not associated with any issues. And in our business each of our time entry must be associated with a pre-defined/authorized by a project manager. We are not the only work that way, believe me :)

Allowing a global timer, may produce entries not associated with tasks. Pretending a user start and stop a global timer without booking is time, thus when the project manager will analyze it timesheets at the end of the week he will ask the employee ; "what did you do between thoses hours...". As a result it will be a nightmare or an impossibility for the employees to recall what he did.

Best regards,

jume-dev commented 10 years ago

Well, i kinda understand your problem. But i am not sure, if this is in a good way fixable. For now, you only can tell your employees to not use the global button :) (Rather use the buttons at the issue page, you can even move time between issues with them. Try starting a timer on an issue, if one is already tracking from another issue.)

We'll try to find a solution.

erakis commented 10 years ago

This could be as simple as you add 1 permissions :

If the user have this permissions it may start timer globally and on issue too.

If this permission is not selected, the user cannot use the the (START TIMER) header top button. Thus, the user can ONLY start timer on assigned issue. This way the time has no choice to be booked when the user stop the timer or switch to another issue.

I would like to help you, but I'm a C# .NET, C++ programmer. I've designed an intranet for our business. This system have several years and works very well, for our need. We present it to some other business and they find it very interesting. However Redmine provides many new features and we evaluated that it would cost less to use Redmine as to update our system.

I'll start reading a book on Rubby very soon and I hope to be able to help the Redmine community :)

jume-dev commented 10 years ago

Well, if you do it your way, there is still the timetracking overview page, where you can start and stop a timer without booking it to a issue. The tracking without booking is in fact the main issue, why we implemented this plugin, cause standard redmine doesn't allow this.

But you are right, something needs to be done. But i am not sure, if your example is the right case. It would be better, if there were a permission to disable timetracking without a booking, but as said this kinda contradicts the whole idea of the plugin.

jume-dev commented 7 years ago

We continue thinking about this in hicknhack-software/redmine_hourglass#7