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

Update get.gov content for renewal feature launch #360

Open
3 of 11 tasks
h-m-f-t opened this issue Feb 3, 2025 · 3 comments
Open
3 of 11 tasks

Update get.gov content for renewal feature launch #360

h-m-f-t opened this issue Feb 3, 2025 · 3 comments
Assignees

Comments

@h-m-f-t
Copy link
Member

h-m-f-t commented Feb 3, 2025

Issue description

When we turn on the renewal feature for our users, we should also update some get.gov content.

Acceptance criteria

Additional context

(Note the one update above in manage.get.gov. I've left it in this repo, though the PR will be over there. It's ok if there's a few day delay in merging that one.)

Links to other issues

No response

@h-m-f-t h-m-f-t transferred this issue from cisagov/manage.get.gov Feb 4, 2025
@h-m-f-t h-m-f-t marked this as a duplicate of #174 Feb 4, 2025
@h-m-f-t h-m-f-t moved this from 👶 New to 🎯 Ready in .gov Product Board Feb 4, 2025
@PaulKuykendall PaulKuykendall moved this from 🎯 Ready to 🔖 Planned in .gov Product Board Feb 6, 2025
@MzBowieFan77 MzBowieFan77 added the carryover Carryover from a previous sprint label Feb 19, 2025
@witha-c
Copy link
Contributor

witha-c commented Feb 28, 2025

@h-m-f-t we'd like to assign this to @witha-k for sprint 65, and you can remain assigned to reflect that you'll be consulted. thoughts?

@h-m-f-t
Copy link
Member Author

h-m-f-t commented Mar 3, 2025

@witha-c but I am bound and determined to do this today!

@h-m-f-t
Copy link
Member Author

h-m-f-t commented Mar 3, 2025

@witha-c @witha-k, I made several suggested edits in the appropriate Google docs and linked to them above. I've checked them off just to represent my initial draft is done. Passing the torch to @witha-k and moving this to 65.

@h-m-f-t h-m-f-t assigned witha-k and unassigned h-m-f-t Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🔖 Planned
Development

No branches or pull requests

4 participants