nextcloud / nextcloud/calendar

Share/Download ICS for single emanation of serial events

Open
#2,862 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage enhancement Feature: Sharing hotspot: recurring events
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Hello,

I would like to make the following feature request:

Settings / Requirements
  • I need to share an ICS file for a single event to an anonymous group of people who are not on Nextcloud users.
  • There exists no mailing list whatsoever, since another system is used to draft and send the e-mail to its recipients.
  • The tool doesn't allow for ICS files to be attached, so link-sharing would be the only way to go.
  • Most events to be shared this way are recurring regularly. However, users are supposed to add to their calendars only one event at a time, not the complete series.
Solution / Workaround
  1. Invite a dummy user to the event and do something to provoke an e-mail invitation to be sent.
  2. Upload the attached ICS file to Nextcloud and create sharing-link for it.

Problem: Step one afaik requires significant change - i.e. event time or date. However, there are other Nextcloud users, that will notice these changes (e.g. will receive notifications) and might become confused. Also, this is very "manual".

Request(s)
  1. In the event sidebar pane, there is a download option. However, for serial events, the resulting ICS is always that for the series. Add a second option to download ICS file for the specific emanation.
  2. Even better solution: Make an event ICS link-sharable, such that there is an option to generate a sharing link for a single event or a single emanation of a serial event.

The generation of single event emanation ICS files must already be implemented somewhere, as such files are automatically attached to e-mail invitations, so I'd think that it's more of a UI task.

It'd be a great improvement to my regular workflow, if either Requests were accepted. I'd also be glad to be pointed to a better solution or workaround, in case I have overlooked it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the event sidebar's existing ICS download option and trace how recurring events are represented. Compare the current series download with the single-emanation ICS attached to invitations, then determine whether the completed work should add a separate download option, an anonymous sharing link, or both.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.