Bug 797404 - event template sets date of event to date of the template
Summary: event template sets date of event to date of the template
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 16
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-25 16:22 UTC by John Griffiths
Modified: 2013-07-21 14:30 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-06-19 19:13:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 294169 0 None None None 2012-06-19 14:38:40 UTC

Description John Griffiths 2012-02-25 16:22:44 UTC
Description of problem:
An event template, when applied to a date, sets the date of the event to the date and time of the template.

Version-Release number of selected component (if applicable):
kdepim-4.7.4-1.fc16.i686

How reproducible:
always

Steps to Reproduce:
1. open the new event dialog to create a new event
2. push manage templates button
3. select a template that was made prior to the current date
4. push apply
5  push OK
  
Actual results:
The dates for the event are changed to the date the template was created. In my case I was creating an event for 2/29/12. My template was created 8/4/2009. The date of the event was changed to 8/4/2009.

Expected results:
The information for the event from the template should have been filled in to the new event but the date and time data should have been left unchanged.

Additional info:

Comment 1 Rex Dieter 2012-06-19 19:13:48 UTC
Good eye spotting https://bugs.kde.org/show_bug.cgi?id=294169

yay, let's continue to track this upstream.

(feel free to reopen if there's some specific need to keep this open downstream)

Comment 2 Sergio Martins 2013-07-21 14:30:59 UTC
Fixed upstream for 4.11.


Note You need to log in before you can comment on or make changes to this bug.