Documentation: Form field requirements

[emilylordahl]

currently blocked by #222

As a form author, I need to configure labels and data limits and be made aware of issues so that I can prevent application errors.

During concept testing, it was observed that builders want control about answer types, including minimum word count because they are worried about preventing and catching errors created in the upload process or their own work, especially in a more complex form, with spacing, numbering, and length can lead to a greater number of errors.

The goal of this ticket is to design robust question settings or similar to provide form authors with control over error prevention.
Consider exploring ways to guide authors towards mistakes to give them support when they might overlook something.

Overview

As a _, I would like _, so that I can _.

Context

Optional: Any reference material or thoughts we may need for later reference, or assumptions of prior or future work that's out of scope for this story.

• [ ]

Acceptance Criteria

Required outcomes of the story

• [ ]

Research Questions

• Optional: Any initial questions for research

Tasks

Research, design, and engineering work needed to complete the story.

• [ ]

Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

• Behavior
  • Acceptance criteria met
  • Implementation matches design decisions
• Documentation
  • ADRs (/documents/adr folder)
  • Relevant README.md(s)
• Code quality
  • Code refactored for clarity and no design/technical debt
  • Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
  • Code is reviewed by team member
  • Code quality checks passed
• Security and privacy
  • Automated security and privacy gates passed
• Testing tasks completed
  • Automated tests pass
  • Unit test coverage of our code >= 90%
• Build and deploy
  • Build process updated
  • API(s) are versioned
  • Feature toggles created and/or deleted. Document the feature toggle
  • Source code is merged to the main branch

Decisions

• Optional: Any decisions we've made while working on this story

[JennyRichards-Flexion]

9/6/24: In conversation with Jim, this item is HIGH priority.

[JennyRichards-Flexion]

@jimmoffet - We looked through this ticket and don't see a clear artifact - but it's listed as HIGH priority. Can you shed some light on what you think this is so we can re-title and reassign it correctly?