Orangutan can be very helpful for employees which use SVN...
What is required for a user to track time? A user must specify work hours, project and maybe issue and a short description...
What does developer which uses SVN do? Runs “update” when comes to the office and runs “commit” when leaves... If we assume that a user always specifies a description when committing (-m) we have a start time, end time and a description! All that we need is project/issue - project can be guessed (or determined if SVN was registered in Redmine) and issue can be extracted from -m message...That is:
- When user does “update” Orangutan starts “tracking”;
- When user goes away and returns Orangutan tracks breaks and saves them somewhere;
- When user commits...
- Orangutan tries to determine the project (if failed the monkey can ask for project later);
- Orangutan tries to determine the issue;
- Orangutan suggests a user to save tasks...
The last is done when there are no conflicts - that is a user did not save any entries for the time a user is believed to work.
That is a user will only be required to answer “yes” per commit (besides the cases when the project is not known)...
#1 Updated by Andriy Lesyuk about 10 years ago
- It will ignore updates between the first update and commit (because it is recommended to always update before commit);
- The first update will be usually a morning update;
- The algorithm can be also changed to treat commit as a start of the task if it (commit) was done at the middle of a working day;