Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide duplicate events / combine them #1329

Open
georgehrke opened this issue Jun 19, 2019 · 8 comments
Open

Hide duplicate events / combine them #1329

georgehrke opened this issue Jun 19, 2019 · 8 comments
Labels
1. to develop Accepted and waiting to be taken care of enhancement New feature request

Comments

@georgehrke
Copy link
Member

georgehrke commented Jun 19, 2019

see nextcloud/server#12501 (comment)

@georgehrke georgehrke added 1. to develop Accepted and waiting to be taken care of enhancement New feature request labels Jun 19, 2019
@georgehrke georgehrke added this to the 2.0.0 - The Vue.js release milestone Jun 19, 2019
@georgehrke
Copy link
Member Author

georgehrke commented Jun 19, 2019

Different aspects to consider when selecting the event to show:

  • highest permission
  • LAST-MODIFIED property
  • If it's an invitation, is it my copy

@georgehrke
Copy link
Member Author

The editor should also show a message that this event is present in Calendar A, Calendar B and Calendar C ...

@Defcon0
Copy link

Defcon0 commented Sep 4, 2019

This is definitely needed. We are currently migrating to Nextcloud calendar but this is the most annoying thing to most users.

@georgehrke
Copy link
Member Author

Please use the Github Reactions feature instead of commenting +1, 👍 etc. These kinds of comments just unnecessarily notify everyone subscribed to this issue. Thx! :)

@georgehrke georgehrke modified the milestones: 2.0.0 - The Vue.js release, 2.0.0 beta4 Dec 9, 2019
@georgehrke georgehrke modified the milestones: 2.0.0 RC, 2.0.1 Jan 14, 2020
@georgehrke georgehrke modified the milestones: 2.0.2, 2.0.3 Feb 27, 2020
@georgehrke georgehrke modified the milestones: 2.0.3, 2.1.0 Apr 2, 2020
@georgehrke georgehrke modified the milestones: 2.1.0, 2.2.0 Sep 4, 2020
@ChristophWurst ChristophWurst modified the milestones: 2.2.0, 2.3.0 Mar 24, 2021
@ChristophWurst ChristophWurst modified the milestones: v2.3.0, v2.4.0 Jun 24, 2021
@ChristophWurst ChristophWurst modified the milestones: v2.4.0, v2.4.1 Nov 25, 2021
@tcitworld tcitworld removed this from the v2.4.1 milestone Dec 17, 2021
@AmonBune
Copy link

Is there any particular reason why this feature request gets pushed from milestone to milestone since 2019?
(The Bountysource Link drops a 404 error by the way @georgehrke )

@ChristophWurst
Copy link
Member

because milestones had been used as wishlist until we realized it creates wrong expectations and removed all unplanned features from milestones. You can read a bit more about this at https://github.com/nextcloud/groupware/blob/main/processes/milestones.md

@AmonBune
Copy link

I understand. Is a bounty needed for this feature to become real? If yes, one of you should reopen the link I guess. I'm sure a lot of people would be happy to see this functionality.

@wolkenschieber
Copy link

When an ICS file is imported multiple times, it often results in duplicate entries in the calendar. These duplicates can be difficult or infeasible to remove manually, especially in cases where there are a large number of events. Implementing a feature to detect and handle duplicate entries during the import process would greatly enhance usability. This could involve identifying and skipping duplicates based on key attributes such as UID, date, time, and event details, or providing an option to remove existing duplicates from the calendar after import. Such functionality would save users significant time and effort in maintaining clean and organized calendars.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Accepted and waiting to be taken care of enhancement New feature request
Projects
None yet
Development

No branches or pull requests

6 participants