As an LFO Industry Reporter, I want to see a list of my facilities, so that I can select the relevant ones for the reporting year

suhafa commented 3 months ago

Description:

Industry Reporters will need to see a list of their facilities and ensure the list is accurate for the reporting year before they can start reporting. Specific for LFOs, doesn't apply to SFOs.

Wireframe here

Acceptance Criteria:

Given I am an Industry Reporter with multiple facilities who has already provided information on my facilities in Registration When I come into the Reporting Module, and have reviewed my Operation information, Then I want to see of all my facilities listed so that I can ensure they will all be captured in my Annual Report.

Given I am an LFO Industry Reporter who is in the Reporting Module If the selected list of facilities is not accurate for the reporting year Then I want the ability to select or deselect facilities from my list so that the correct facilities are selected.

Note: We are not adding the "Past facilities belonging to this operation" in this card for now, just the facilities that are currently related to an operation. We should add a follow up card to add that piece later on.

Development Checklist:

[ ] The list of facilities for an operation is derived from the erc.facility_ownership_timeline table
[ ] Facilities can be checked/unchecked via the page UI
[ ] Facility data is saved to the erc.report_facility table when checked
[ ] Facility data is deleted from the erc.report_facility table when unchecked
[ ] 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

Notes:

-

patriciarussellCAS commented 1 month ago

@suhafa - I wrote some draft AC for this card. Let me know if these make sense to you. It still needs work but it's a start I think.

rdromey commented 2 weeks ago

@suha to add link to wireframe @dleard to add dev checklist

bcgov / cas-reporting