search

bcgov / foi-flow

Freedom of Information modernization
Apache License 2.0
5 stars 3 forks source link

Download Request/Event Queue as a .csv or excel #3679

Open m-prodan opened 1 year ago

m-prodan commented 1 year ago

Assumptions & Scope We heard a lot of feedback from users when showing the event queue, that they would love to be able to download their queue as an excel document. We have heard similar comments in the past from Ministry users as well, especially when using the advanced search feature for overdue requests, or specific date range searches.

We should make it such that the record the user downloads is the easiest from a dev perspective, whether that is csv or excel.

What is IN scope? Downloading the results of the request or events queue as a PDF Feature/function should work for both the general request/event queue and for advanced search results

design needed - will need a design to basically show where the "download" button should live

Acceptance Criteria

Scenario 1: Download Request Queue - My Requests

Scenario 2: Download Request Queue - My Team's Requests

Scenario 3: Download Request Queue - Watching Requests

Scenario 4: Download Events Queue - My Requests

Scenario 5: Download Events Queue - My Team's Requests

Scenario 6: Download Events Queue - Watching Requests

Scenario 3: xxxxxx ...

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Design @xxx - please link the Design here

Definition of Ready

  1. [ ] Is there a well articulated User Story?
  2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
  3. [ ] If there is a user interface, is there a design?
  4. [ ] Does the user story need user research/validation?
  5. [ ] Does this User Story needs stakeholder approval?
  6. [ ] Design / Solution accepted by Product Owner
  7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
  8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
  9. [ ] Has the story been estimated?

Definition of Done

  1. [ ] Passes developer unit tests
  2. [ ] Passes peer code review
  3. [ ] If there's a user interface, passes UX assurance
  4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
  5. [ ] Confirm Test cases built and succeeding
  6. [ ] No regression test failures
  7. [ ] Test coverage acceptable by Product Owner
  8. [ ] Ticket ready to be merged to master or story branch
  9. [ ] Developer to list Config changes/ Update documents and designs
  10. [ ] Can be demoed in Sprint Review
  11. [ ] Tagged as part of a Release
  12. [ ] Feature flagged if required
  13. [ ] Change Management activities done?
lmullane commented 1 year ago

Ha! I was thinking the same thing based on the feedback.

m-prodan commented 1 year ago

Moving this up the new issues list - might just be missing a design for where the export/download feature lives. I wouldn't prioritize this over anything else yet, but will remove incomplete AC as I don't expect that to change too much.

m-prodan commented 1 year ago

Note from refinement - couple ways we could handle this... building from ground up in app (high point of around 21) - risks include scale of data being pulled, it could create performance concerns if someone opts to pull a report with a significant number of requests/lines.

Alternative solution - Redash report... limitation is it will be daily. Estimate for ReDash would be around 13 - would need to get full requirements.

Ultimately the load issue will come from wanting the live data - so need to be clear about that.