-
Notifications
You must be signed in to change notification settings - Fork 19
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
#2728: domain manager page updates [BOB] #3078
Conversation
🥳 Successfully deployed to developer sandbox bob. |
🥳 Successfully deployed to developer sandbox bob. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<p> | ||
Domain managers can update all information related to a domain within the | ||
.gov registrar, including security email and DNS name servers. | ||
.gov registrar, including contact details, senior official, security email, and DNS name servers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment: Looking at the copy from the Figma, the bullet point with "All domain managers will be notified when updates are made to this domain." needs to be removed.
response = self.client.get(reverse("domain-users", kwargs={"pk": self.domain.id})) | ||
self.assertContains(response, "Domain managers") | ||
self.assertContains(response, "Add a domain manager") | ||
# assert that the non-portfolio view contains Role column and doesn't contain Admin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment: Update comment to that this is the portfolio view and that it doesn't contain Role column and does contain Admin tag
🥳 Successfully deployed to developer sandbox bob. |
🥳 Successfully deployed to developer sandbox bob. |
Ticket
Resolves #2728
Changes
Context for reviewers
Setup
Code Review Verification Steps
As the original developer, I have
Satisfied acceptance criteria and met development standards
Ensured code standards are met (Original Developer)
Validated user-facing changes (if applicable)
As a code reviewer, I have
Reviewed, tested, and left feedback about the changes
Validated user-facing changes as a developer
Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.
As a designer reviewer, I have
Verified that the changes match the design intention
Validated user-facing changes as a designer
References
Screenshots