Hello
If the status is change by multiple update the result is not the same like click-change the status next to the "creation information" or the normal moving to next status.
E.g. when switching the status by multiple update to cancelled only the field "status" changes to canceled, but when you do it over the interface e.g. of an activity the checkbox "in progress" plus the date and the checkbox "closed" plus the date and the checkbox "cancelled" are set too.
If it comes to the workflow it checks it correctly, e.g. from copied it is not possible to go directly to cancelled. One has to switch to recorded first and from there cancelled is possible.
Or if closed/cancelled requires a result it will ask for the result first.
It would be helpful to have the same method behind the multiple update and save time.
Regards
I cannot reproduce.
On V9.2.2 behavior is as expected.
What version do you use ?
9.2.2 is in use
I think this has to do with checklists.
I tried on the Demo with default "Task" activity. --> OK
I tried on our system with default "Task" activity --> OK
I changed to a specific activity with checklist (some points required for done state) --> Failed --> effect as described before.
I changed to the default "Developer" activity --> ok
I changed to a specific activity with checklist (some points required for done state) --> Failed --> effect as described before.
It is just that the whole change is rejected : some controls (checklist required) fail and then reject the update
The big difference is even if the required boxes which are required for done state are checked, the update fails and compared to other updates where e.g. the field for Result is mandatory, a feedback on the screen is generated that it was failed.
And it still changes the state.
And the separate update of the other fields by multiple update is successful to achieve the same as individual state switching.
Also as I wrote already, if the activity is opened (single) and the state is changed there is no reject and everything is fine...
Another anomaly is e.g. that if there is left over work a normal ticket cannot be switched to cancelled and it complains and reports this.
And there is the same behavior like I wrote in the beginning, when you perform multiple update it switch the state, aborts the rest but doesn't show anything that faild and reports updated in the activity stream.
Hi,
I can confirm that there is an issue : multiple update does not control mandatory cjhecklists
Ticket #5676 recorded
But for tickets with left work, setting status to cancelld (or closed or even done) automatically sets left work to zero, so there is no blocking.