This is a space where the community of Teamwork users can ask for support, explanations,
and also vote up or down questions, answers and feature requests.
>> Back to Teamwork's site.

I do not understand the planning. I describe three scenarios: Scenario 1: I have a task that runs between 13 and 20 December. Today is 22. In the planning, set for each day of the following: 11:40, 12:50, 14:35, 17:30, 23:20 and 40:50. I do not understand where they come from these calculations. This task has an estimated time of 35 hours assigned to a single resource that works 7 hours per day. No timesheet for this situation.

Scenario 2: In the following scenario, I make a timesheet for 7 hours on day 13, and the distribution that is as follows: 10:30, 10:16,11:40, 14:00, 18:40 and 32:40.

Scenario 3: Now I delete the previous timesheet and make a new one on 15 also 7 hours. The distribution is as follows: 10:30, 11:40, 13:25, 14:00, 18:40 and 32:40.

Why and how do these calculations and on the other hand, what involvement they have in these, the worklogs approved.

This is a problem with this release and you solved in next release?

Thanks for the quick response

This question is marked "community wiki".

asked Dec 22 '10 at 11:10

Angel's gravatar image

Angel
666

edited Dec 22 '10 at 11:13


At the moment there is a bug in the planning which has been fixed and it will be out in the next Teamwork release, out soon.

The new release will include also a new chapter of the guide describing with more details how the operator load amd plan work.

This answer is marked "community wiki".

answered Dec 23 '10 at 05:17

Silvia%20Chelazzi's gravatar image

Silvia Chelazzi ♦♦
408519

edited Dec 23 '10 at 05:18

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

×60
×23
×5

Asked: Dec 22 '10 at 11:10

Seen: 356 times

Last updated: Dec 23 '10 at 05:18

| Teamwork faq | about | contact us | Teamwork blog | Teamwork documentation | feedback always welcome