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
Remove "Draft domains" section from the navigation for analysts.
This section displays the domain names that appear in a domain request. Cameron noted this section of the admin does not need to be exposed to analysts anymore.
Acceptance criteria
"Draft domains" is removed from the navigation for users with "analyst" permission
Analyst is still able to edit the "requested domain" via the domain-request page.
"Websites" is removed from the navigation for users with "analyst" permission
Analyst is still able to edit "alternative domains" via the domain-request page. (Note: "current websites" are no longer editable via the domain-request page for analysts; that should remain as is)
Additional context
This is an update that came out of the recent audit of Django field labels. And from user feedback gathered during the Diary Study.
vickyszuchin
changed the title
Django admin: Remove "Draft domains" section from the navigation for analysts
Django admin: remove "Draft domains" section from the navigation for analysts
Mar 29, 2024
Added "refinement" label. Need to determine how the field can still be edited within a request ... after the section is removed from navigation. Also determine whether the "websites" section should be removed from navigation, as well.
Katherine-Osos
changed the title
Django admin: remove "Draft domains" section from the navigation for analysts
Django admin: Remove "draft domains" & "websites" sections from the navigation for analysts
Apr 1, 2024
Issue description
Remove "Draft domains" section from the navigation for analysts.
This section displays the domain names that appear in a domain request. Cameron noted this section of the admin does not need to be exposed to analysts anymore.
Acceptance criteria
Additional context
This is an update that came out of the recent audit of Django field labels. And from user feedback gathered during the Diary Study.
Links to other issues
Related to: #1924
The text was updated successfully, but these errors were encountered: