Version: (using KDE 4.3.2) Installed from: Ubuntu Packages Simple annoying bug. Goal === Move a contact with subcontacts/meta-contacts. EXAMPLE1. How to Reproduce ============ 1. Select contact and change its meta-contact. 2. select the appropriate other meta-contact. 3. Now a single contact is grouped with multiple protocol IM. 4. Now try drag and drop the contact(which has metacontacts) to another folder/group. Result is the contact doesn't move to new group. Expected Behaviour ============ 1. Select contact and change its meta-contact. 2. select the appropriate other meta-contact. 3. Now a single contact is grouped with multiple protocol IM. 4. Now try drag and drop the contact(which has metacontacts) to another folder/group. Result should be the contact(which has metacontacts) is moved to the new folder/group. EXAMPLE2. How to Reproduce ============ 1. Select contact and change its meta-contact. 2. select the appropriate other meta-contact. 3. Now a single contact is grouped with multiple protocol IM. 4. Now right click the contact(which has metacontacts) and go to groups => move to => select a group. Result is the contact doesn't move to new group. Expected Behaviour ============ 1. Select contact and change its meta-contact. 2. select the appropriate other meta-contact. 3. Now a single contact is grouped with multiple protocol IM. 4. Now right click the contact(which has metacontacts) and go to groups => move to => select a group. Result should be the contact(which has metacontacts) is moved to the new folder/group.
Are all account of that metacontact online? We don't allow user to move contact when account is offline.
No, they not all online. Why don't you allow it? Its a bit unrealistic to expect all contacts to always have all protocols signed it at once in order to move a contact. Surely there is another way or this can be fixed?
Could someone please confirm this bug report? It shouldn't be unconfirmed when it can be so easily reproduced 100% of the time.
This bug should be confirmed...
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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 mark the bug 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 has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!