nextcloud / nextcloud/calendar

Import confirmation on target calendar

Open
#2,571 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage enhancement Feature: Importing
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.
The behaviour of the autoselected calendar before importing is dangerous. It doesn't ask the user to confirm the choice again and has no intelligent suggestion. Also the search box might provoke a wrong target calendar. A a result a users bulk inserts items to calendar / todo , which he can't undo / remove easily.

Describe the solution you'd like
Don't preselect existing calendars for imports anymore. Let users actively select (and maybe confirm?) the desired calendar.
If you offer more intelligence (e.g. look for name strings of existing calendars within filename - useful to imports), let user confirm the import, so he doesn't doubleclick by mistake.

Describe alternatives you've considered

  • Preselect new calendar? (But I don't know a merge 2 calendar feature within NC, so the result might be not useful as well ... but at least non-destructive)
  • Ask to undo after a import?

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

No files or tests are named. Start by tracing the calendar import flow and its target-calendar selection and search behavior; define the confirmation and non-destructive default before implementation. Done means imports require an intentional target choice or confirmation and avoid accidental bulk insertion.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.