Download Request/Event Queue as a .csv or excel

* As an IAO or Ministry User
* I want to be able to download my request or event queue as a csv or excel file
* so that I can easily create a spreadsheet quickly

**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**
* GIVEN a user is on their "My Requests" filter
* WHEN they click on the download button
* THEN a download will trigger for a (Excel or CSV) document
* AND the document will include the columns and data from the queue in the sheet

**Scenario 2: Download Request Queue - My Team's Requests**
* GIVEN a user is on their "My Team's Requests" filter
* WHEN they click on the download button
* THEN a download will trigger for a (Excel or CSV) document
* AND the document will include the columns and data from the queue in the sheet

**Scenario 3: Download Request Queue - Watching Requests**
* GIVEN a user is on their "Watching Requests" filter
* WHEN they click on the download button
* THEN a download will trigger for a (Excel or CSV) document
* AND the document will include the columns and data from the queue in the sheet

**Scenario 4: Download Events Queue - My Requests**
* GIVEN a user is on their "My Requests" filter
* WHEN they click on the download button
* THEN a download will trigger for a (Excel or CSV) document
* AND the document will include the columns and data from the queue in the sheet

**Scenario 5: Download Events Queue - My Team's Requests**
* GIVEN a user is on their "My Team's Requests" filter
* WHEN they click on the download button
* THEN a download will trigger for a (Excel or CSV) document
* AND the document will include the columns and data from the queue in the sheet

**Scenario 6: Download Events Queue - Watching Requests**
* GIVEN a user is on their "Watching Requests" filter
* WHEN they click on the download button
* THEN a download will trigger for a (Excel or CSV) document
* AND the document will include the columns and data from the queue in the sheet

**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?

Start by locating the request and event queue views, including their advanced-search result paths, and review how the active filter data is assembled. Confirm the download format and button placement with the missing design and product owner. Done means each listed filter downloads a file containing the queue columns and data, with unit and acceptance tests passing.

Written by the indexing model from the issue text.