bcgov / bcgov/reserve-rec-admin

Quick links to other tools/products

Open
#44 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Reservations
Dominant language
TypeScript
Stars
3
Forks
7
Avg merge
15h 29m
Merged PRs (30d)
29

Description

User Story:

As an admin or park operator, I want quick links to the other products/tools/services that I need to access to enter or update information related to my parks.

Acceptance Criteria:

Given
When
Then

Given
When
Then

Development Checklist:
  • ...
  • ...
  • ...
Dependencies
  • Blocked by
  • Blocking

Wireframe(s):

Workflows:

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

  • User story is included
  • User role and type are identified
  • Acceptance criteria are included
  • Wireframes are included
  • Design / Solution is accepted by Product Owner
  • 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:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, wireframes, links, placement, or acceptance criteria are provided. First clarify which tools should be linked, where the links belong, who can see them, and what behavior and accessibility requirements define completion.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.