department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

Setup accept/deny page #74374

Closed cohnjesse closed 8 months ago

cohnjesse commented 9 months ago

Note: Renamed from "Implement first draft of accept/deny page" since we are using the term "placeholder page" instead of "first draft"

Description: Since we know we will need a UI for a VSO to approve or deny a 21-22 request we should go ahead and do a first pass of this page. The details of what this page looks like are very much in flux so this first pass can just be the building of the basic page component and some dummy content. Alternatively if you want to check in with design and see what the direction they are going with this page is and implement a simplified version of it, that is ok too as a stretch goal.

User Story or Problem Statement: As a VSO I need to be able to approve or deny a 21-22 request so that I can provide Veterans with the benefits and services they need.

Implementation Details: Since this is such an early version of this page the engineer that pick this ticket up has some latitude for what they want to put in this page. The page should be built as a component inside /representatives/containers and use some basic routing/ navigation so that we can go from the dashboard to this page.

Mockups/Designs: At the time of writing this there is no mockup however design may have some direction on this so the engineer that picks this up is encouraged to start a Slack thread with design to get their opinions.

Prerequisites/Dependencies: None at this time.

Blockers: None at this time

Specifications: This should be built as a container component and use some basic routing to go back and forth between this page and the dashboard page.

Acceptance Criteria:

Testing Criteria: We will most likely just need some basic e2e tests that test that the page is there and that the components and routing are present and work.

Automated Testing: This will need to be tested to 100% coverage as detailed by the command yarn test:coverage-app {app-name}

Accessibility (A11y) Testing: Confirm that accessibility testing is completed.

Documentation: Documentation will be covered in a subsequent ticket

nihil2501 commented 8 months ago

PR