Load tag design

[csstarling]

Background As an LEO, I need load tags to contain basic information that I need in order to ensure compliance: Quantity removed, date removed, permit number that matches the permit issued.

We’ll also want the tag to be visible from a distance and to include instructions on how to tag the load, and how to distinguish this year’s permit from last year’s, but we’re planning to break those into separate stories.

This story covers the basic permit design.

Acceptance criteria

• [x] LEOs can match the tag to the corresponding permit
• [x] Load tag allows permit holder to indicate quantity removed
• [x] Load tag allows permit holder to indicate date product removed

Tasks

• [x] Design and test low fi mocks
• [x] Design refines mocks based on research insights
• [x] Validation of acceptance criteria completed
• [x] Design review - [ ] Manual accessibility testing complete
• [ ] PO Approved

Definition of done

• [ ] e2e tests are updated for application routing changes.
• [ ] e2e tests are functioning.
• [ ] Child routes for existing pages are working.
• [ ] Pull requests meet technical definition of done.
• [x] Usability tested.

[csstarling]

Link to design debt in wiki and initial (very rough) tag design

[carlsonem]

@aQuib where do this issue stand? Looks like we weren't able to start it this sprint as planned

[aQuib]

@MelissaBraxton - Can I get access to this document?

[aQuib]

Removed 'Manual accessibility testing' since it should be performed on the PDF generated by the system which is apart of the development/engineering requirements for #184

[Rebekah-Hernandez]

Here is the updated load tags. I am currently looking into which forests will need different ones based on location. Load Tag v3.pdf

[Rebekah-Hernandez]

@aQuib I moved this into validation, but I'm not sure about marking off the Definitions of Done

[aQuib]

We intend to use only pattern for the MVP, and three patterns for phase two of the application.

[MelissaBraxton]

@aQuib - Are there any new issues to address feedback from last week's testing? The first iteration story is complete, but I think you may be working on refinements? Once we have new issues documenting any refinements, we can move this card to ready for main.

[aQuib]

@MelissaBraxton - Yes, there are refinements based on usability testing results. I have created an issue for the load tag enhancement which can we refine during our backlog grooming. Moving this issue to 'Ready for Main'