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

VOTE-2810, VOTE-2811, VOTE-2812 state content field changes #1001

Merged
merged 8 commits into from
Sep 26, 2024

Conversation

daniel-crowder
Copy link
Contributor

@daniel-crowder daniel-crowder commented Sep 24, 2024

Jira ticket

VOTE-2810 - New field type
VOTE-2811 - New block type
VOTE-2812 - Update State Content type

Description

Add a new custom compound field. Add new fields to the State content type using the new compound field. Create a new block type using the new compound field along with other field types.

Deployment and testing

Post-deploy steps

  1. Run 'lando retune' locally

QA/Testing instructions

  1. Login as an admin
  2. Goto content admin page and edit a state content item
  3. Locate the new tab, "State display content"
  4. Confirm the available fields match the document located in https://cm-jira.usa.gov/browse/VOTE-2811
  5. Add content to the fields and confirm that it saves
  6. Edit the state again and confirm that the fields display in the fields
  7. Goto content admin page again and go to block types
  8. Locate the "State Display Content" link
  9. Click the manage fields link and confirm the available fields match the document located in https://cm-jira.usa.gov/browse/VOTE-2812
  10. Go back to the block types page and click the button up top to create a new block
  11. Add a "State Display Content" block type
  12. Fill out the form, save, and confirm that the block saves successfully
  13. Edit the block and confirm that the fields display

Checklist for the Developer

  • A link to the JIRA ticket has been included above.
  • No merge conflicts exist with the target branch.
  • Automated tests have passed on this PR.
  • A reviewer has been designated.
  • Deployment and testing steps have been documented above, if applicable.

Checklist for the Peer Reviewers

  • The file changes are relevant to the task objective.
  • Code is readable and includes appropriate commenting.
  • Code standards and best practices are followed.
  • QA/Test steps were successfully completed, if applicable.
  • Applicable logs are free of errors.

@daniel-crowder daniel-crowder marked this pull request as ready for review September 25, 2024 21:08
@rayestrada rayestrada changed the title Feature/vote 2810 state content field VOTE-2810, VOTE-2811, VOTE-2812 state content field changes Sep 26, 2024
…agov/vote-gov-drupal into feature/vote-2810-state-content-field
@rayestrada rayestrada merged commit 249391d into dev Sep 26, 2024
3 checks passed
@rayestrada rayestrada deleted the feature/vote-2810-state-content-field branch December 3, 2024 00:17
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