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

Remove submitter from Domain Requests and Domain Info #2162

Closed
6 of 11 tasks
abroddrick opened this issue May 13, 2024 · 4 comments · Fixed by #2693
Closed
6 of 11 tasks

Remove submitter from Domain Requests and Domain Info #2162

abroddrick opened this issue May 13, 2024 · 4 comments · Fixed by #2693
Assignees
Labels
carryover Carryover from a previous sprint dev issue is for the dev team Feature: 👤 User Profile

Comments

@abroddrick
Copy link
Contributor

abroddrick commented May 13, 2024

Issue description

Creator will now be used to send emails (#2157) and at this point #2156 will have informed any user whose request is still active that their previous contact email (aka the submitter email) will no longer be used. We can now go ahead and just delete the submitter from Domain Request, Domain Info and any lingering places where it is still being used like unit tests, comments and fixtures

Acceptance criteria

  • remove any contact associated with a submitter (this should be a migration file not a script)
  • remove submitter from models (domain Request/domain info)
  • remove submitter from references in comments and unit tests
  • remove submitter from fixtures
  • regenerate our database schema image without submitter in it
  • remove any other reference to submitter not mentioned above

Additional context

No response

Links to other issues

@abroddrick abroddrick added the dev issue is for the dev team label May 13, 2024
@PaulKuykendall PaulKuykendall moved this from 👶 New to 🎯 Ready in .gov Product Board May 13, 2024
@therealslimhsiehdy therealslimhsiehdy added the blocked Is dependent on another issue and cannot be worked label Jun 27, 2024
@therealslimhsiehdy therealslimhsiehdy self-assigned this Jun 27, 2024
@vickyszuchin vickyszuchin moved this from 🎯 Ready to 🔖 Planned in .gov Product Board Jul 2, 2024
@vickyszuchin vickyszuchin moved this from 🔖 Planned to 🎯 Ready in .gov Product Board Jul 3, 2024
@vickyszuchin vickyszuchin removed the blocked Is dependent on another issue and cannot be worked label Jul 3, 2024
@abroddrick
Copy link
Contributor Author

marking this as blocked as we need to wait until the user profile feature is turned on. @vickyszuchin does product have a ticket for evaluating the profile ? We could block this one by that.

@abroddrick abroddrick added the blocked Is dependent on another issue and cannot be worked label Jul 18, 2024
@therealslimhsiehdy therealslimhsiehdy self-assigned this Jul 23, 2024
@vickyszuchin vickyszuchin moved this from 🎯 Ready to 🔖 Planned in .gov Product Board Jul 23, 2024
@vickyszuchin vickyszuchin removed the blocked Is dependent on another issue and cannot be worked label Jul 29, 2024
@vickyszuchin
Copy link

Removed "blocked". The dependencies on other tickets have been resolved.

@therealslimhsiehdy therealslimhsiehdy moved this from 🔖 Planned to 🏗 In progress in .gov Product Board Aug 5, 2024
@erinysong erinysong self-assigned this Aug 20, 2024
@vickyszuchin vickyszuchin added the carryover Carryover from a previous sprint label Aug 20, 2024
@vickyszuchin
Copy link

This ticket was moved from sprint 51 to sprint 52 during Sprint 52 kickoff meeting.

@vickyszuchin
Copy link

Moved to current sprint (Sprint 53).

@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in .gov Product Board Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment