Bug 172788 - Sort by latest changes
Summary: Sort by latest changes
Status: REOPENED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-14 11:57 UTC by Dotan Cohen
Modified: 2021-03-09 02:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dotan Cohen 2008-10-14 11:57:31 UTC
Version:            (using KDE 4.1.2)
Installed from:    Ubuntu Packages

In Kaddressbook there should be an option to sort contacts by latest changes. There are several instances in which this would be useful:
1) A new contact is added, and then some time later the user does not remember the contact's name or other details.
2) The user makes an error entering data, and the contact is not where it is expected to be in the list.
3) Someone else puts her cute little hands on the keyboard and pushes buttons, imitating daddy. Now daddy has to fix the damage.
4) The user must export latest changes via vcard. He can sort by latest change, select the latest contacts, and only export those.

I personally have been in all four of these situations, and I am certain that there are other use-cases where this feature would be helpful.
Comment 1 Tobias Koenig 2009-08-05 16:38:34 UTC
The development of the old KAddressBook will be discontinued for KDE 4.4.
Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.
Comment 2 Dotan Cohen 2009-10-16 11:41:50 UTC
Moving Product to the new KAddressBook as the feature request is still valid. Thanks!
Comment 3 Justin Zobel 2021-03-09 02:34:12 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.