Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent use of username when sharing an address book #592

Closed
ghost opened this issue Aug 10, 2018 · 1 comment · Fixed by #596
Closed

Inconsistent use of username when sharing an address book #592

ghost opened this issue Aug 10, 2018 · 1 comment · Fixed by #596
Labels
3. to review Waiting for reviews bug Something isn't working
Milestone

Comments

@ghost
Copy link

ghost commented Aug 10, 2018

There is an inconsistency between calendar and contacts app when sharing a calendar or address book. In the Calendar app the full name (Bill Gates) of the person you share to is shown. However in Contact app, only the user name (bgates) is visible. I think that the full real name should be shown and not user names.

@nextcloud-bot
Copy link
Member

GitMate.io thinks possibly related issues are #422 (read-only view broken in shared address books), #64 (Address book data lost when any user receiving a share is deleted), #171 (Add possibility to create virtual address book), #494 (disable shared address book does not work), and #556 (Search/Create Contacts/Address Book not possible).

@skjnldsv skjnldsv added this to the 3.0.0 milestone Aug 22, 2018
@skjnldsv skjnldsv added bug Something isn't working 1. to develop Accepted and waiting to be taken care of labels Aug 22, 2018
@skjnldsv skjnldsv mentioned this issue Sep 11, 2018
26 tasks
@skjnldsv skjnldsv added 3. to review Waiting for reviews and removed 1. to develop Accepted and waiting to be taken care of labels Sep 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants