[Design] [ADMIN] Facility revenue report

Design work description and context:

2nd priority of financial reports.

Report purpose - view each day's pass reservation and revenue data of one or more selected facilities within a selected data range. Each row represents a day or arrivals for a facility.

Visuals are a nice to have. The key is the need to export to excel and where we will access the reports within the admin tool.

Details in Nan's Mural board of reporting requirements. Link can be found through Confluence.

Acceptance Criteria:

• Review requirements outlined by user research
• Reach out to researcher for any needed clarification & to develop solutions/approaches
• Design program deposit report
• Review designs with SMEs for input
• Review designs with dev team for input
• Update designs as required for input

Dependencies:

• Related to https://github.com/bcgov/reserve-rec-admin/issues/91
• Blocked by https://github.com/bcgov/reserve-rec-admin/issues/15
• Blocking

Relevant documentation as reference:

• MVP [admin] requirements - Confluence (under Reporting subheading)
• Mural board titled 'Financial Reporting Workspace' (note: have not linked due to privacy)
• Wiki data model

Notes:

• Work outlined in this phase of the design workflow will involve sketches, ideas, rough designs, potential blue sky solutions

Definition of Ready: Design ticket

• Acceptance criteria are included
• Relevant documentation to context is linked

Definition of Done: Design ticket

• Designs are peer reviewed by another designer
• Designs are reviewed by developers
• Design is reiterated based on feedback, as needed

PO Review pipeline:

• Acceptance criteria are checked by Product Owner
• Approved by Product Owner

Start with the linked Confluence requirements, the Financial Reporting Workspace Mural board, and the API wiki data model. Confirm the dependency on issue 15 and clarify requirements with the researcher before designing. Done means the report designs are peer reviewed, reviewed by developers, updated from feedback, and approved by the Product Owner.