Database - New Template Table Fields

[k-macmillan]

User Story - Business Need

We need two new fields in the template and template history table to store strings for:

• html

• text

• Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a service using VA Notify
I want consistent emails regardless of internal updates
So that we can provide a consistent experience to Veterans

Additional Info and Resources

• Postgres Character Types

Acceptance Criteria

• Both fields are the Postgres type: text (unlimited chars)
• Both fields are optional
• Field names relate to their use (html and text), they do not have to be "html" and "text"
• _html field is visible in the database for the templates and template_history tables
• _text field is visible in the database for the templates and template_history tables
• This work is added to the sprint review slide deck (key win bullet point and demo slide)

QA Considerations

Potential Dependencies