1. When a To-do item is created using a template and then it is subsequently opened for editing, the "Start" and "Due" times (the term "Time" is used here in the generalized sense: yyyy MM dd hh mm) change to the current values for the year, month, and day while the hour and minute seem to change randomly regardless of the times that were originally entered.
2. Hence, every time a To-do item is opened for editing, it becomes necessary to re-enter the "Start" and "Due" times that were originally entered in order preserve the times in the original To-do item.
3. This is extremely inefficient and greatly reduces the usefulness of Korganizer.
Steps to Reproduce:
1. Using the "Template" feature create a To-do item with appropriate content including "Start" and "Due" times (the term "Time" is used here in the generalized sense: yyyy MM dd hh mm).
2. Save and close the To-do item.
3. Open the To-do item and observe the "Start" and "Due" times.
1. The "Start" and "Due" times change.
1. The "Start" and "Due" times must not change.
1. Linux > Kubuntu > version 13.10 was used.
2. The problem occurs only when a template is used to create the To-do item.
I can reproduce this bug with Korganizer 4.14.6 (Kubuntu Vivid beta, fully updated as of 2015-03-26)
This bug has never been confirmed for a KDE PIM 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.
The template feature in Korganizer 5.4.3 seems to be broken, so I can't try to reproduce the bug. I created a new template called 'Test Template', and when I try to apply it to a new To-do I get a dialog saying "Unable to find template ''.", and my desktop locks up.
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.
For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.
Thank you for helping us make KDE software even better for everyone!
This bug is still present in KOrganizer 5.7.3 (Kubuntu 18.04).
Still present in 5.9.1. Spoiler: will still be present in 5.9.2. It also happens for events, so I move this from component todoview to incidenceeditor.
I just learned about incidence templates in KOrganizer, which kind of puzzles me after having used KOrganizer for quite some time now... Templates do not appear anywhere other than the incidence editor: not in any menu and neither in the preferences. Discoverability could probably be improved. Still not sure if I use templates correctly.
Git commit ba964b3b52028423b5434058490f8a5062c18072 by Glen Ditchfield.
Committed on 01/04/2022 at 01:45.
Pushed by gditchfield into branch 'release/22.04'.
Preserve datetimes of incidences created from templates
When the editor applies a template, as identified by the "isTemplate"
property, it (usually) does not copy its start/end/due datetimes; it
keeps the datetimes set before the template was applied. Unfortunately
when the instance is saved it still has the "isTemplate" property, and
so when it is edited the editor does not copy its datetimes; the GUI
fields are left with default values. Removing the property fixes the
M +1 -0 src/incidencedatetime.cpp
*** Bug 367910 has been marked as a duplicate of this bug. ***
*** Bug 345380 has been marked as a duplicate of this bug. ***