[L] A&R: Add Date Range search/filter to export data page

[JLWade]

Description:

As a bc parks staff who uses A&R, I would like to export a specific date range in a standard report so that I do not download all the data from A&R.

This ticket is to add a date range filter (from admin library) to the export report standard report tab.

downloading an A&R standard report is getting big, especially when users do not need to see all data from all years.

Acceptance Criteria:

Given I am a A&R admin user (role dependent for what data is downloaded) When I go to the export report page Then I see an option to select a date range OR export all data on the standard report tab.

Given I am an A&R admin user (role dependent for what data is downloaded) When I go to the export report page and select date range for standard report download Then I can select a specific date range by year and month to download.

Development Checklist:

• [ ] ...
• [ ] ...
• [ ] ...

Dependencies

• Blocked by https://github.com/bcgov/bcparks-ar-api/issues/326
• Blocking

Wireframe(s): Figma Design

• the filter should only be available if Export All is unchecked.
• Prototype for dropdown behaviour is unavailable

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:

[Dianadec]

Q for team in refinement: Does something like this need a separate design ticket, or is it straight forward enough to embed the full implementation in this one card? cc @JLWade

[Dianadec]

Refinement Notes:

• 99% of the time the export is just for the most recent data.
• Prefers to export a set of months (eg: Jan-March as an example of a set)
• Rarely would they need to export the whole thing
• Ideal: Specify months. April data; May Data, etc
• Remove Export all or no? - New staff might not know when the data starts... eg: January 2017 is when the data first starts
• Keep Export All

Next steps:

• creating design ticket
• refining this ticket according ot the notes above.

[meyerdarcie]

Designs in ticket #338

[Dianadec]

Blocked by SAM release.

[Dianadec]

This may have been a duplicate of this one - https://github.com/bcgov/bcparks-ar-admin/issues/265