You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of freedomofpress/securedrop#4425 and freedomofpress/securedrop#4459, we have support for setting a first name and last name for a given Journalist Interface user, and for retrieving this data via the API. First and last name are optional, and are not used for authentication.
The first use case for this data is the "AuthWidget", the area in the top left of the client that shows who's currently logged in, and that provides access to signing out via a caret menu.
If first name and last name are set, the client should use this information instead of the username, both for showing the initials, and for the long form display of the username next to the initials.
Given that a first name and a last name are configured for my account When I log into the SecureDrop Client Then the first name and the last name should be shown, instead of my username And the initials should be derived from my first and last name, instead of my username.
Given that a first name and a last name are not configured for my account Then the behavior should be the same as before (username and username-derived first two letters).
User Story
As any user, when I am signed into the SecureDrop client, I want to see my first and last name reflected in the UI, because that feels more human and natural than seeing my username or email address.
(With the sprint load as high as it is, flagging that this is a good candidate to get bumped off the sprint, so let's treat it as lower priority relative to other tasks for now.)
This task is blocked pending completion of SDK support (freedomofpress/securedrop-sdk#87).
As of freedomofpress/securedrop#4425 and freedomofpress/securedrop#4459, we have support for setting a first name and last name for a given Journalist Interface user, and for retrieving this data via the API. First and last name are optional, and are not used for authentication.
The first use case for this data is the "AuthWidget", the area in the top left of the client that shows who's currently logged in, and that provides access to signing out via a caret menu.
If first name and last name are set, the client should use this information instead of the username, both for showing the initials, and for the long form display of the username next to the initials.
See the screens tagged authwidget for the design spec.
Acceptance Criteria
Given that a first name and a last name are configured for my account
When I log into the SecureDrop Client
Then the first name and the last name should be shown, instead of my username
And the initials should be derived from my first and last name, instead of my username.
Given that a first name and a last name are not configured for my account
Then the behavior should be the same as before (username and username-derived first two letters).
User Story
As any user, when I am signed into the SecureDrop client, I want to see my first and last name reflected in the UI, because that feels more human and natural than seeing my username or email address.
[See the user stories spreadsheet for current prioritization of this functionality.]
The text was updated successfully, but these errors were encountered: