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

Automaticaly start/stop time counting #42

Open
dskibarko opened this issue Jul 17, 2016 · 4 comments
Open

Automaticaly start/stop time counting #42

dskibarko opened this issue Jul 17, 2016 · 4 comments

Comments

@dskibarko
Copy link

Plugin will be better if automaticaly start/stop time counting were present if task status transient detected.
This very actuality for Redmine there Agile board used. Time start/stop will be from agile.
For example describe main idea:

  1. If Task status chаnged to "working", then timer start counting time for this task.
  2. If Task status chаnged from "working" to over(should be administrator configured), then timer stop counting time for this task.
  3. If "Task N" status chаnged to "working" and for over task "Task M" time is counting, then
    • "Task M" automaticaly moved from "working" to "pause" status(should be administrator configured)
    • Stop time counting for "Task M" (because only one job can be in progress).
@speedy32129
Copy link
Owner

I'm currently in development of a branch that is adding multiple loggers or timers (optionally configured by administrator).

The next phase is multiple transitions. So if a developer starts a task the status will update from open to working then when the developer stops working on it it will go back to the previous status open.

If I get your drift your asking for status change based on when someone manually changes the status to something different. you want to automatically end the existing logger and start a new one?

@dskibarko
Copy link
Author

Yes, main idea -> time counting for task if task in state "working".
Some people was used JIRA (on previous company) and JIRA time logging is baised on current task state "working".
Multiplle transition (MP-method described by you) is good solution to.
May be should be better to have both methods (you MP-method and JIRA-method)???

@dskibarko
Copy link
Author

Hi! Have you a progress or not?

@dskibarko
Copy link
Author

Hello,
what about good songs feature "The next phase is multiple transitions. So if a developer starts a task the status will update from open to working then when the developer stops working on it it will go back to the previous status open."???
Is it in progress?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants