Enhance activity app backend to collect and display more information about event change
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Hello,
we've migrated our calendars from an old groupware to Nextcloud and are missing a function that the old system had: in Nextcloud Calendar and the Activity Stream it isn't possible to see some kind of changelog of single events. As shared calendars often are used to reserve rooms, cars or other resources by many users today it isn't possible to see the history of changes to a calendar entry.
My idea was to open a feature request in nextcloud/calendar (https://github.com/nextcloud/calendar/issues/2636) as some information (user, event name, calendar name and time of change) are already visible in the activity stream but are not shown when I open the detail view of a single event. Because the existing information does not seem to give back a complete changelog what happened to a event I was asked to open an issue here.
Ideally this information should be logged in the activity stream and thereby should thereby be accessible by the calendar app:
Creation of an event (already shown in activity stream):
- User
- Date and Time
Modification of an event (partially shown in activity stream at the moment):
- User
- Date and Time
- Difference between the old and new version of the event (for example: modification of start / end time, changes made to the name of the event, the description field, invitation ecc.).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the activity app backend's existing calendar event entries and how the calendar app reads activity details. Define how creation and modification history should expose the user, timestamp, and old/new event differences, then verify the information is complete for event changes and accessible from the calendar view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100