[L] View Site Record

[Dianadec]

Description:

As a BC Parks Admin user, I would like to view a Site Record so that I can find the information I need.

Acceptance Criteria:

Given that I am a BC Parks Admin User When I view a Site Record Then I can see its Legal name and Historical name information

Given that I am a BC Parks Admin User When I view a Site Record Then I can see breadcrumbs at the top of the page showing me that this is a subpage of the associated Protected Area

Given that I am a BC Parks Admin User When I view a Site Record Then I can see an Edit button

Development Checklist:

• [x] Page title will be a combination of the ID and the Legal Site Name. ID should be in bold text.
• [x] The system generated details (Type, Status, Last updated) are below the title
• [x] The Legal name data are the same data points used for Protected Area Names. the same rules apply.
• [x] Historical names for sites work the same as for Protected Areas. That is, Historical Name section is generated when a user goes through the Change Legal name flow and saves changes.
• [x] The Edit button, upon clicking, has a dropdown with three options: Minor edit, Legal name, Repeal

Wireframe(s)

• https://www.figma.com/file/qdjegD6YHWZPlyFT8dGXvk/Data-Register?type=design&node-id=3299%3A5591&mode=design&t=zk1gqGE2sJkNs6Ea-1

• Clickable prototype for Edit dropdown: https://www.figma.com/proto/qdjegD6YHWZPlyFT8dGXvk/Data-Register?type=design&node-id=4361-116757&t=KRBDpucZHEPKgzYq-0&scaling=min-zoom&page-id=4361%3A116641&starting-point-node-id=4361%3A116757

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

• [x] User story is included
• [x] User role and type are identified
• [x] Acceptance criteria are included
• [x] Wireframes are included
• [x] Design / Solution is accepted by Product Owner
• [x] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

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

• 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 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:

• This piece was broken out from the original ticket: https://github.com/bcgov/parks-data-register/issues/124
• Questions and Answers captured in Figma:

Dependencies

• Blocked by
• Blocking

[Dianadec]

I have updated the ticket description based on the edit dropdown solution update

[manuji]

QA Notes:

• Deploy the code to TEST environment (Use the repo: https://github.com/bcgov/parks-data-register)
• Link to test environment: https://test-data.bcparks.ca/admin/
• Verify the items given in the ticket description.
• If passed, please move to PO review and assign to @JLWade

[jpeersoxd]

Tested on TEST. No further issues found. Moving to PO Review.

[JLWade]

mving to done