Skip to content

Create UI Design for ApproveGuestWebUI

License and Copyright Notice

By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).

Pre-checklist

  • I have searched for, and did not find, an existing issue at the top-level.

Stories

Story 1: As a user I want the UI to be streamlined so that the application is intuitive to use.

Ready checklist

  • Independent (of other issues in flow)
  • Negotiable (and negotiated)
  • Valuable (the value to an identified role has been identified)
  • Estimable (the size of this story has been estimated using /weight value or the menu on the right)
  • Small (can be completed in 50% or less of a single iteration)
  • Testable (has testable acceptance criteria)

Also

  • Appropriate role labels have been applied (e.g., role:*).
  • Relevant activity labels have been applied (e.g., activity:*).
  • Linked to related issues, epics, and milestones.

Diagrams

Full Resolution PDF: ApproveGuestWebUIFilters.pdf
ApproveGuestWebUI_dropdown_example.pdf image image

Acceptance Criteria

Scenario: [3-5 word description of scenario]
  Given I am a developer creating the ApproveGuestWebUI
  When I am implementing the front end application
  Then I have a model to work from

Tasks

  • School logo
  • Guest Info component
  • Button to approve guest
  • Guest Search component
  • Button to deny approval
  • Button to approve another guest
  • Button to close page

Template Version 2.0.0

Edited by John Pacheco