saving Calendar event in Tracker field type 'Calendar event' scraps changes of other Tracker fields

• Conflict of two features (each works well independently)
• Consistency
• Usability

Releated to: item8186-to-be-synched-fetched-event-details-of-of-Calendar-event-and-details-in-a-Tracker-item-with-Tracker-field-Calendar-item

The cause:

Given a Tracker has a field of type 'calendar item' and a number of other fields, for example a 'Textarea' or a 'Textfield'...

Given a user creates a Tracker item and desides to add an event to the Tracker item, then the user can edit the Calendar event from inside the tracker, after the Tracker item is saved the first time (with existing event).

It is quite probable that a user who wants to edit a Calendar event might need to edit another field of the same tracker item at the same time.

Looking at the UI of the Tracker form, a user would most likely asume, that he can add or edit data in the Textarea, then edit and save the event and then save the Tracker item without losing any data.

In fact, when the user clicks at the edit-event button and then the save-event button, __all changes made to the Tracker item in the other fields will be lost.

Observation:

After saving the event, the whole page (browser tab) reloads the non-edit version of the page, instead of only saving the Calendar details to the Calendar and keeping the other field's data 'alive'.
Thus if you have filled a form or edited fields previously filled and then edit the event and then save the event, the just filled data get's completely lost

I imagine, that there would be some kind of AJAX event needed that pushed the Calendar event data to the database, without reloading the page.

Depending on the respective Tracker form, this could cause the loss of work and thus frustrate users to some unreasonable extent.

This bug has been demonstrated on show2.tiki.org

Please demonstrate your bug on show2.tiki.org

This bug has been demonstrated on show.tikiwiki.org

Please demonstrate your bug on show.tikiwiki.org