Bug 339013 - Creating event using 'Create event' button does not store date info
Summary: Creating event using 'Create event' button does not store date info
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: calendar (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-11 13:32 UTC by Ondrej Holecek
Modified: 2018-02-01 09:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ondrej Holecek 2014-09-11 13:32:33 UTC 
When I use buttons "Create Event" and "Create To-Do" from KMail interface to create events, if I change date information this date info is not stored in created event. It defaults to current date and time.

Reproducible: Always

Steps to Reproduce:
1. enable Create Event button in KMail taskbar
2. use Create Event button to create new event
3. change event date and time information
4. check the date and time of created event

Actual Results:  
Date and time information is set to current date and time.

Expected Results:  
Date and time information is set to those specified during event creation.

Kontact version 4.14
Comment 1 luisfe 2014-11-03 11:27:44 UTC 
I can confirm this on debian testing,  kmail 4.14.1
Comment 2 Denis Kurz 2017-06-23 19:37:14 UTC 
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:51:03 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.