I notice a weird behavior that can be pretty impacting:
Use case:
You have a ticket T1 that belongs to activity A1
You start to record work on that ticket and working time is counted in the activity A1
You change (using mass update changes button) the ticket T1 to activity A2
==> The time recorded withint the ticket does not update the activity A1 (it should decrease) and the activity A2 (it should increase).
Is there a daily update maybe ?
Is there no update at all ?
In fact Planning Activity should not be changed where real work is entered.
That is why Planning Activity is locked on the interface.
You found a workarond to chenge the Planning Activity, but the is an invalid change.
It should be refused.
By the way, you can fix the activities with a small change of work (add and after remove some work on one ticket)
Hi, does it mean, you'll fix it by throwing an exception in mass update mode when a ticket as a planning activity recorded with work on it ?
Yes, it is the idea.
It will not be an exception but a control message, but the idea is there.