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

VEBT-911 SCO - Update 'Last Updated' date #2384

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

mghisilieri
Copy link
Contributor

Summary

This ticket/PR involves updating the Last update field on the SCO page in the footer to 2024-12-10. It will show on the UI as December 10, 2024.

Related issue(s)

As a...

VEBT Developer

I want…

To update the last updated date of the SCO page

So that…

The SCO page can reflect the latest date

Acceptance Criteria

Update the 'Last Updated' date to December 10, 2024.
To be confirmed shortly -> On the top, remove the yellow box entirely.

Technical Details:

Dependencies:

Feature Flag needed: No

Demo needed: No

UAT needed: No

Additional Notes:

Testing Details:

( X ) Quick Turn Around/Direct to Production

( ) Remains in Staging

( ) Staging Environment unavailable, coordinate w/ developer

Requested by and when:

Kate, 12/09

Definition of Done:

( ) Demo/UAT completed with EDU

( ) Passed all internal testing in Staging

( ) Passed all internal testing in Production

( ) All work documented in Jira ticket

Testing done

The content-build repo was built and served locally, where the Last updated date appeared successfully in the footer.

Screenshots

Before:

Last updated (Before)

After:

Last updated (After)

What areas of the site does it impact?

Resources for Schools

Acceptance criteria

Quality Assurance & Testing

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Linting warnings have been addressed
  • Documentation has been updated (link to documentation *if necessary)
  • Screenshot of the developed feature is added
  • Accessibility testing has been performed

Error Handling

  • Browser console contains no warnings or errors.
  • Events are being sent to the appropriate logging solution
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

  • Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

N/A

@mghisilieri mghisilieri requested review from a team as code owners December 10, 2024 22:07
@jsimonVA jsimonVA self-requested a review December 12, 2024 14:24
Copy link
Contributor

@jsimonVA jsimonVA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants