You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is not posible to update the Status an event in agenda as "Not aplicable" instead "to do"
This means that every upodated event will be transformed ina a task "to do" even is not a task.
Environment
Version: 14.0.1
OS: Linux64
Web server: Apache/2.4.46 OpenSSL/1.1.1g mod_jk/1.2.41 mod_bwlimited/1.4 mod_fcgid/2.3.9 Phusion_Passenger/5.3.7
Now is possible to create manual events in the agenda to register the content of a Telephone call for example, and register the event with Status as "non applicable", that is very convenient since is not a task to do, is just the registration of an event.
But unfortunately, if you modify the event to update any data, then the status is switched to a type "to do", and then the event is converted as a task to do, even is not a task.
Steps to reproduce the behaviour
Create a manual event in the agenda with status/percentage type as "not applicable"
Modify/update the event after creation
Observe that is not possible to save it with the status/percentage type as "not applicable" any more.
The text was updated successfully, but these errors were encountered:
Bug
Is not posible to update the Status an event in agenda as "Not aplicable" instead "to do"
This means that every upodated event will be transformed ina a task "to do" even is not a task.
Environment
Expected and actual behaviour
Now is possible to create manual events in the agenda to register the content of a Telephone call for example, and register the event with Status as "non applicable", that is very convenient since is not a task to do, is just the registration of an event.
But unfortunately, if you modify the event to update any data, then the status is switched to a type "to do", and then the event is converted as a task to do, even is not a task.
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: