search

nextcloud / calendar

📆 Calendar app for Nextcloud
https://apps.nextcloud.com/apps/calendar
GNU Affero General Public License v3.0
988 stars 240 forks source link

Show changelog of event in detail view #2636

Open cm-schl opened 4 years ago

cm-schl commented 4 years ago

Hi,

we're migrating a calendar from an old groupware to Nextcloud and are missing a function: in Nextcloud Calendar it seems that it isn't possible to view a changelog of a single event. Our old groupware did show the name of the person that created or changed the event with some additional info (date, time of the action and also what has been changed) in a list. We found out that in the Activity view it is possible to see the last changes, but this isn't a solution when you need to check the modifications made on an event created a year ago for a future event (example: we sometimes have to create calendar entries for events that take place in two years from now).

As the information itself seems to exist in the activity stream is there maybe a simple solution to show the changes also in the single event (some sort of filter that shows all entries of the activity stream for one event)?

tcitworld commented 4 years ago

The activity stream currently doesn't keep event update details, only the date and the user performing creation/update/deletion. The deletion information wouldn't make much sense (since the event doesn't exist anymore), therefore the information in the changelog (creation & update without details) wouldn't be much of use.

So we would first need the activity app backend to collect and display more information about event change. Do you mind opening an issue on https://github.com/nextcloud/server/issues/ to ask about this?

cm-schl commented 4 years ago

Hi, although it isn't a lot of information already this data could be interesting for shared calendars as thereby you can see when a event was created, by whom and if after the creation the event has been modified. For example if a calendar is used to reserve rooms you can see if a reservation has maybe been created after an other reservation and so on.

I fully agree that the deletion information doesn't make sense as the event doesn't exists anymore.

I will gladly create an issue for the backend side - but maybe the reduced functionality described above could be also useful already for other users? Would it make sense to start with the reduced function?