Version: (using KDE KDE 3.0.3) Installed from: RedHat RPMs OS: Linux When editing to-do list item categories in KOrganizer, it should detect if any items are assigned to that category ans either ask if they should be updated or just go ahead and updated them. Example - I recently renamed a categpry from "Auto" (which was ambiguos) to "Car Maint.". I already had 5 to-do items inthat category. They did not get changed but remained "Auto" which was no longer a valid category. There is no way to update them so I had to manually go thru each one of them... Keep up the great work!
Maybe a solution would be to add a replace option to the find events fuinction. This way you could perform a find for all "Auto" categories, then choose "replace" and type "car-maint" and have it change them all. Another option would be the ability to click and edit and drop down for the catagories colum on the List view so you could list everything, sort by catagories and change them there.
Replaced chris.arrowood@cybertivity.com with null@kde.org due to bounces by reporter
Similar issue with deleting a category. That category will keep resurecting itself unless you manually remove the "CATEGORY:<cat>" line from the calendar file. At rename or delete time perhaps you should be prompted to rename/delete the category for all existing entries. This is with korganizer 3.5.3.
Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list.
Bug confirmed in KDE4.
*** Bug 251427 has been marked as a duplicate of this bug. ***
Still around in 4.9! - When you delete a category, it will show up again as long as anything was tagged with it. - Same thing when you turn a category into a subcategory. The category will be duplicated because the change was not communicated to the affected events. I think this bug should receive a "Confirmed" flag and be assigned a relatively high priority. It's such a show stopper to any real work with categories. It makes t almost impossible to use categories in any advanced manner.
Not trivial to fix, but I might pick this up for 4.13
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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.
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.