LFO Reporter: Facilities Table Page

[pbastia]

Description:

Wireframe + flow here

Acceptance Criteria:

**NOTE to Devs: The "actions" column on this table should act the same was as the one on the "Reporting Dashboard". See tickets #274 and #296 and #219

Given I am an LFO industrial reporter who has reviewed my list of facilities (#197 ) When I click continue from the "review facilities" page Then I am brought to the facility table page, where all the facilities I had previously selected are displayed with the information as shown in the wireframe

Given that I am an LFO industrial reporter on the Facility table page When I click on "Start" in the actions column for a facility Then I am brought to "Review Facility Information" page for that facility and a report has been started for that facility.

Development Checklist:

• [ ] Add a facility table page at /reports/{version}/facilities that displays facilities selected on the "review facilities" page.
• [ ] Display facility data from the "Review Facilities" page with columns: Facility Name, Facility Type, Facility BCGHG ID, Status, and Actions.
• [ ] Implement search for each column: Facility Name, Facility Type, Facility BCGHG ID, Status.
• [ ] Ensure the "Actions" column behavior matches the "Reporting Dashboard" functionality, as per tickets (#274, #296, #219).
• [ ] Store and update facility report status (Draft, Completed, Not Started), add a field in facility report table for status.
• [ ] On clicking Start, navigate to the Review Facility Information page and set the report status to Draft.
• [ ] Meets the DOD

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 (if required)
• [ ] Design / Solution is accepted by Product Owner
• [ ] 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)

• [ ] Acceptance criteria are tested by the CI pipeline
• [ ] UI meets accessibility requirements
• [ ] Configuration changes are documented, documentation and designs are updated
• [ ] Passes code peer-review
• [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
• [ ] Ticket is ready to be merged to main branch
• [ ] Can be demoed in Sprint Review
• [ ] Bugs or future work cards are identified and created
• [ ] Reviewed and approved by Product Owner

Blocked By

197

Notes:

-

[suhafa]

Wireframe added

[rdromey]

@ayeshmcg to take a first pass at this