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

DIGITAL-60: add field to guide content type #78

Merged
merged 4 commits into from
Dec 27, 2024

Conversation

cathybaptista
Copy link
Contributor

@cathybaptista cathybaptista commented Dec 16, 2024

Jira ticket

DIGITAL-60

#Relates to

Digital-43
Digital-61

Purpose

Acceptance Criteria:

A dropdown text field that allows a single glossary vocabulary ID to be referenced

QA/Testing instructions

  1. Pull branch

  2. Drush CIM

  3. lando rebuild && lando si

  4. Taxonomy module should be enabled.

  5. Under the guide content type, make sure the field HCD Glossary is available and that it is set up to reference a vocabulary ID.

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.

@cathybaptista cathybaptista force-pushed the feature/DIGITAL-60-add-field-to-guide-content-type branch from a9987ce to 4a96c35 Compare December 17, 2024 15:30
@cathybaptista cathybaptista marked this pull request as ready for review December 17, 2024 16:03
@cathybaptista
Copy link
Contributor Author

@mattsqd let me know if you didn't want 61 to be based on 60 and 60 on 43. Just trying to save work, but may have just made some instead.

1 similar comment
@cathybaptista
Copy link
Contributor Author

@mattsqd let me know if you didn't want 61 to be based on 60 and 60 on 43. Just trying to save work, but may have just made some instead.

@cathybaptista cathybaptista changed the title Feature/digital 60 add field to guide content type DIGITAL-60: add field to guide content type Dec 17, 2024
@cathybaptista cathybaptista force-pushed the feature/DIGITAL-60-add-field-to-guide-content-type branch from 7df6020 to 45a157e Compare December 27, 2024 19:35
@omerida omerida merged commit 580e3e3 into develop Dec 27, 2024
2 checks passed
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