nextcloud / nextcloud/calendar

Preserve calendar name when importing from link

Open
#7,835 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem? Please describe.

When creating a new calendar using the "New subscription from link (read-only)" in a target Nextcloud instance and the origin calendar has been exported from another Nextcloud instance via subscription link (I didn't try with other systems, but the behaviour should be similar), the name of the calendar is not preserved. Instead, the name of the calendar in the target instance is named as the origin Nextcloud instance.

If the same calendar is imported in Thunderbird, the name is correctly preserved.

Describe the solution you'd like

I'd like to have the name of the calendar preserved, as it happens in another major CalDAV client, such as Thunderbird.

The user can always rename the calendar in his/her instance, but it would be great to preserve as default name the name assigned by the calendar creator.

Describe alternatives you've considered

No response

Additional context

Nextcloud Server 32.0.3
Calendar 6.1.3

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

Reproduce the issue through “New subscription from link (read-only)” using a calendar exported from another Nextcloud instance, then trace the subscription import entry point. Compare the imported calendar name with the origin name and Thunderbird’s behavior; done means the origin calendar name is preserved by default.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.