[kaddressbook] [Bug 332358] New: Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)

[Fuchs]

https://bugs.kde.org/show_bug.cgi?id=332358

            Bug ID: 332358
           Summary: Regression: Baloo for tags messes up categories/groups
                    when syncing with external collections (e.g. owncloud)
    Classification: Unclassified
           Product: kaddressbook
           Version: 4.13 pre
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs at kde.org
          Reporter: develop at fuchsnet.ch
                CC: tokoe at kde.org

Slightly related to https://bugs.kde.org/show_bug.cgi?id=331896

due to the new usage of baloo instead of nepomuk for tags  (in kaddressbook:
called categories) now the akonadi tag is saved in the contact. 

Previously it was saved as: 

BEGIN:VCARD
CATEGORIES:Family
UID:0KqAvlaaZq
VERSION:3.0
END:VCARD


BEGIN:VCARD
CATEGORIES:akonadi:?tag=1
UID:1af9e6d2-f1ec-46fc-bcdc-26831c28b332
VERSION:3.0
END:VCARD

This leads to problems when syncing with other sources, e.g. owncloud and quite
probably also other groupware, because they then use that as the group name. 

Reproducible: Always

Steps to Reproduce:
1. Create a new category, e.g.  "Family" 
2. Assign this category to a contact from a groupware ressource, e.g. owncloud
instance
3. Let owncloud sync that with other devices, e.g. a mobile phone
Actual Results:  
The contact ends up in the new group  "akonadi:?tag=1" and is displayed as that
on all synced devices. 

Expected Results:  
The contact ends up in the group "Family", as it did prior to  4.13 

Marking this as major, since most of these sources do auto-sync, hence after an
update it's likely that you sync broken data to a lot of devices

-- 
You are receiving this mail because:
You are the assignee for the bug.