Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability to restart a ticket #8

Closed
DaNiSoFt opened this issue Mar 30, 2010 · 12 comments
Closed

ability to restart a ticket #8

DaNiSoFt opened this issue Mar 30, 2010 · 12 comments
Labels

Comments

@DaNiSoFt
Copy link

Would be nice to have the ability to enter a comment
OR to restart a ticket instead of entering a comment

Extra:
A list of running tickets where only one ticket can be active

@delaitre
Copy link
Collaborator

What do you mean by "restart a ticket" ?
If you just want to restart the current time tracker, you can click on "stop #xxx". This will redirect you to the "log spent time" page. Here, you just have to click to another page and the time will not be logged.
I know this is far from ideal, but I did not find a good way to "restart" the time tracker. I mean, I though to add a "cancel" link next to the "close" link, but I think it will take too much space in the menu. Maybe a hierarchical menu will be better (I think this is the better solution) but I didn't have the time to try that yet.

For the "extra", I didn't undestand your request... can you describe it more precisely ?

@DaNiSoFt
Copy link
Author

For example an restart-link where the ticket just starts on that time where it was stopped.

For extra:
If I stop a ticket and maybe start an other ticket and did not enter a time for the stopped one...

the stopped ticket appears in a list where it is possible to save, restart or cancel
time tracking.

@delaitre
Copy link
Collaborator

If I understand correctly, this is more a "continue" link than a "restart" one. However, I didn't think this is really useful.
The only use case which comes in my mind will be if you forget to start the time tracker for your current task. However, there is a lot of chance that you don't want to track the time from the last stop, and it this case, the "continue" link will be helpless.

For your extra:
When you stop the time tracker, the spent time field is pre-filled with the time tracker value (indeed, this is THE feature of this plugin, this is why I wrote it!). Thus, you don't have to "enter" a time for the stopped issue. You just have to select an activity, and validate the new "spent time" entry.
To start the time tracker on another issue, you have to stop it for the current one. Thus, if you fall into the situation where you start the time tracker on another issue, and you don't save the spent time of the last tracked one, I can't do anything for you (and, really, you didn't use the plugin as it is design for).

The plugin was designed to have a really simple and smooth workflow. Keeping an history of the time trackers and so, or adding feature which are not well defined or really useful is conflicting with this plugin nature.

@DaNiSoFt
Copy link
Author

Yes it is to continue the time what I mean.

And to be able to start more than one ticket
but only one actually running per user
(the others are stopped in "background")

Therefore there could be a list like:

Ticket 1 (running) - 0.25h - [stop] - [save] - [cancel]
Ticket 2 (stopped) - 1 h - [continue] - [save] - [cancel]
Ticket 3 (stopped) - 2 h - [continue] - [save] - [cancel]

the running ticket always is in the menu on top

If one ticket gets continued - the running one is stopped

For me it often happens that work on more than one project
or task on one day.....

but I also see that it is some work to do.
And unfortunately my time also is quite rare.

@delaitre
Copy link
Collaborator

Ok, it's clearer in my mind now :)
Your use case is quite common indeed, thus I'm starting to love your idea.
Moreover, I'm really not happy with the current flow to "cancel" a time tracker, yours is better.

A remark though: When using the "continue" option, the time spent is, in reality, ceased. When you'll "save" the time tracker, the spent time logged is a continue one. I don't think Redmine check if the log time entries doesn't overlap, thus we could log it without problem, but this will not reflect the realty of the time spent. However, this should be ok for most user.

As it requires some work to do, I'd like to hear what other users think about this feature.

At time being, I personally open one tab by ticket in my browser, and I switch from one to the other when needed... not ideal but this is better than without the plugin :)

@DaNiSoFt
Copy link
Author

First I want to say that I like Ur plugin very and it makes it much easier to track time !

What I mean is:
If I spent already 0.25 h on a ticket and press continue than the tracking should
start with 0.25 h for that ticket again.

If the "save" button is pressed the user should be able to write ONE
comment to the sum of times.

@delaitre
Copy link
Collaborator

Yes, this is what I understood.
Forget what I say about time overlapping, this will probably never happen since the time log form doesn't require a "start time", but only the day of the work. Thus, time overlapping could occurs only if you run a time tracker longer than a day which should not happen.

@delaitre
Copy link
Collaborator

delaitre commented May 4, 2010

I think I will finally implement this feature some day as it will simplify my workflow too. Don't now when though.

@ghost
Copy link

ghost commented May 6, 2010

Please integrate this feature. It will be very useful, just some kind of pause on current issue and then continue the work.
Big thanks for your module!

@kalbasit
Copy link

+1 on this request, thanks for your effort!

@delaitre
Copy link
Collaborator

delaitre commented Feb 9, 2011

Little update just to let you know that you can pause/resume the current time tracker now.
However, multiple per-user time trackers is not implemented yet.

@delaitre
Copy link
Collaborator

delaitre commented Dec 5, 2011

I'm closing this issue as the stop/resume feature is implemented. The issue #61 will be used to discuss the "multi-tracker" feature.

@delaitre delaitre closed this as completed Dec 5, 2011
creich referenced this issue in hicknhack-software/redmine_time_tracker Jul 12, 2012
time_list_controller now removes unwanted filters from the filter_list
make time_bookings belong_to project
added missing dependency to time_log => time_bookings (missed "delete_all")
added some translations
added migration #8
added project_patch
cleaned the code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants