Activities Taking Less Than a Day

Thanks for your answer.

babynus wrote:

How can I deal with Acitivities which will only take about a few hours at most?

You can : just enter assigned work as hours... Planning will take it into account.
Don't mind about duration : projector always calculate durtion in days... so smallest duration is 1 day, even if it really takes 1 hour.

Ok.

However this means that Activities estimated to take only 1 or 2 hours cannot be used in planning as such - for planning, they will always take at least about a day, right?

babynus wrote:

Are Activities supposed to be larger chunks of work? If so, how do I model small "Activities" in ProjeQtor?

Yes. It is plroject management, not exploitation management.
Good scale for tasks, in my opinion is 5-10 days.

Ok.

So if I have a bunch of smaller issues / todos, I could combine them into a single, larger Activity and document them there.

However, I then would have to manually keep track about the resolved and still open TODOs within this Activity. An example would be an Activity which has 10 sub-TODOs.

I'm also not quite sure how I would handle it if those TODOs are actually implemented / execute by different Resources which I do not exactly know before - an Activity is always assigned to a single responsible Resource, I think...

Maybe I could use Tickets to model this? Those could then also be linked to an Activity for time/effort tracking, if I understood the manual correctly?

How is it handled in this case if the tickets are assigned to and resolved by different resources - will the Activity stay unassigned, or will each Ticket have to be linked to an Activity assigned to the same responsible Resource as the Ticket?

babynus wrote:

However this means that Activities estimated to take only 1 or 2 hours cannot be used in planning as such - for planning, they will always take at least about a day, right?

No, duration will be displayed as 1 day, but planned work will take just 1 or 2 hours.

I'll then probably use the "Tickets linked to an Activity" approach in the future.

But just to make sure I understood you correctly:

This is possible also for future estimation / planning, before any work has been booked on / assigned to this Activity?

Possibly I still haven't understood some concepts correctly then - as the screenshot I have posted shows, I can only enter estimated efforts in whole days, not hours.

So how to I specify an estimated amout of, say, 2 hours for an Activity, so it's considered with only 2 hours during planning?

And, another question:

What happens with Tickets which are not assigned to any Activity?

How (if at all) are those considered during planning,

and where does the real work time assigned to those end up?