Bug 1021368 - account displayname should be unique
Summary: account displayname should be unique
Keywords:
Status: CLOSED DUPLICATE of bug 967392
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: develop
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-21 07:43 UTC by wangjing
Modified: 2018-02-06 00:41 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-21 07:47:41 UTC
Embargoed:


Attachments (Terms of Use)
screenshot for comment0 (64.35 KB, image/png)
2013-10-21 07:43 UTC, wangjing
no flags Details

Description wangjing 2013-10-21 07:43:13 UTC
Created attachment 814453 [details]
screenshot for comment0

Description of problem:
account displayname should be unique because displayname was used to display on the other places on web, if they are not same, then it's confused.

Version-Release number of selected component (if applicable):
beaker-devel Version 0.15.0

How reproducible:
always

Steps to Reproduce:
1. add two account1, account2 and set the same displayname to them.
2. add both of them to one account's submission delegates table.
3. check the account name on web.

Actual results:
after step1, both of them are prompted "*displayname* saved".
after step3, there are two same accounts in the submission delegates table on the web.

Expected results:
hope the displayname to be unique.

Additional info:
except the example in step1-3, there are also other places used displayname, so it's an issue.

Comment 1 Nick Coghlan 2013-10-21 07:47:41 UTC
Duping this onto 967392, since always displaying the username (which is already guaranteed to be unique) with the display name shown in a tooltip is our preferred approach to resolving this.

*** This bug has been marked as a duplicate of bug 967392 ***


Note You need to log in before you can comment on or make changes to this bug.