Value Statement

As a user, you should be able to run "reports" from the search results. The goal is to provide the ability to export search results as csv.

Export options:

• Export via AcmTable. Easily reusable throughout ACM UI. Doesn't fully capture search results, as search result tables are by kind.
• Export entire search result (from search header?). This captures entire search result. Could be harder to reuse as some pages use a combination of search data and recoil data (ex: Apps)

Outstanding questions:

1. For exported search results. Should the csv include just the search result table headers? Or should it be all resource data saved in search that might not appear in the table?
2. Different resources have different fields saved in search - can we have multiple tables in a csv?

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.