A&R: ability for rec services/admin to add sub areas

Description:

This ticket is for the ability within A&R for admin users to add sub-areas to support increased day use traffic counter data that will be collected soon (49 counter installed in South Coast) without a developer request each time. There are a mix of trail and traffic counters (majority are trail), impacting data under "vehicle count" and "trail count".

Acceptance Criteria:

• Ability to admin user (rec services only) to add new sub-area

Development Checklist:

• ...
• ...
• ...

Dependencies

• Blocked by
• Blocking

Relevant documentation as reference

Definition of Ready

• Acceptance criteria are included
• Wireframes are included (if applicable)
• Design / Solution is accepted by Product Owner (if applicable)
• Dependencies are identified (technical, business, regulatory/policy)
• Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • UI meets accessibility requirements
  • Unit tests are written
  • Work is traceable in GitHub
  • PR linked to ticket number
  • If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • Code is peer reviewed and has passed CI/CD tests
• QA:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • Code is potentially shippable to the production environment
  • Functional features have been tested and passed by QA
  • UI components tested by designer
  • Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • Reviewed and approved by Product Owner

Notes:

Start by reviewing the A&R admin workflow for creating sub-areas and clarifying the incomplete acceptance criteria with the product owner. Identify the UI and data entry points involved, confirm how Rec Services-only access is enforced, and define tests for adding a sub-area and using it for trail and vehicle counter data.