Minor question:
I noticed that the manner in which real work is logged differs between Tickets and Meetings - is that expected behaviour ? (I don't see any impact, but it's not very consistent).
- Create ticket T1 , with planning activity = A_TCK
- Create periodic meeting PM1, with planning activity = A_MEET
- Log work on T1 and on PM1#1
- Run report "detailed work per resource":
=> the real work on Ticket is displayed as work on the planning activity A_TCK
=> the real work on Ticket is displayed as work directly on the meeting, without mention of the planning activity A_MEET
(see attached)
As I said, very minor, but maybe for consistency of future developments it would be best to standardize the approach (in table 'work', use refType = 'Activity' and idWorkElement to refer to the meeting).
Note : saw this in the V5 I'm using, but tested the same on V6.
It is not really inconsistent, and really designed this way.
Meetings are planned items : you can assign work, plan meeting to reserve work for resources, ...
It is this way as Meetings can be plan as soon as project is decided.
Tickets are not planned because they are not know at project start.
So you cannot plan work on tickets. Either, you plan work on an activity, and then you'll attach ticket to activity as Planning Activity. This will group work on ticket on activity, and reduce left work on planning activity : it will subtract real work on ticket....
Hope this is more clear.
Yes, it's clear, thanks ! 🙂
Mistake on my part, I thought the Meeting was indeed unplanned (workelement) , while in fact it is. So, it's perfect ! :woohoo: