Bug 268130 - Event with same name gets replaced
Summary: Event with same name gets replaced
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.4.10
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-10 13:54 UTC by viliam.ganz
Modified: 2017-01-07 22:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description viliam.ganz 2011-03-10 13:54:25 UTC
Version:           4.4.10 (using KDE 4.6.1) 
OS:                Linux

If i have an event with recurrence etc. and I import from kmail invitation an event with same name. The original gets replaced and all other occurences are replaced. This is very annoying cos i have regular meetings scheduled and if one occurence is postponed then all of my other occurences are deleted. This way i lose all infos and have to create it or sth else.

Reproducible: Always

Steps to Reproduce:
1. Accept invitations with regular occurence
2. Accept invitation with same event name just with one occurence

Actual Results:  
All other occurences are deleted - only the newly accepted remains

Expected Results:  
KOrganizer asks what to do - whether to replace all, or replace specific event or add as new occurence/event

The invitations are most likely created by Outlook. I would really like to have this fixed as this is very annoying to me.
The distro is Archlinux, installed from arch repos.
Comment 1 Denis Kurz 2016-09-24 18:43:34 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:39:13 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.