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

[Eng] Retitle and describe My Forms page #487

Open
24 tasks
racheledelman opened this issue Feb 25, 2025 · 0 comments
Open
24 tasks

[Eng] Retitle and describe My Forms page #487

racheledelman opened this issue Feb 25, 2025 · 0 comments
Labels
story User story

Comments

@racheledelman
Copy link

Overview

As a builder, I would like to know understand what content is on the forms list, so that I can understand what I'm looking at.

Context

Both this page and the Forms Index are lists of forms. We need to differentiate between these pages.

Image

Acceptance Criteria

Required outcomes of the story

  • The page is titled and headlined "View and edit forms"
  • There is a description below the headline that reads"This page contains all the forms that your organization has created on the 10x Forms Platform."
  • After the Forms Index is live, show a second sentence: "For a list of all forms, including PDFs, see the Forms Index." that links to wherever the Forms Index lives

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story User story
Projects
None yet
Development

No branches or pull requests

1 participant