Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[STORY]: Admin export of all org's input files #2477

Closed
8 tasks
ClaireValdivia opened this issue Jan 19, 2024 · 2 comments
Closed
8 tasks

[STORY]: Admin export of all org's input files #2477

ClaireValdivia opened this issue Jan 19, 2024 · 2 comments

Comments

@ClaireValdivia
Copy link
Contributor

ClaireValdivia commented Jan 19, 2024

Full User Story

As a USDR Admin User, I want to export all of an organization's historic input files that were used in treasury reports so I can enable partners to meet compliance standards for keeping reporting files stored for several years after a grant is complete.

Additional Context:

  • We are already storing input files, but not in a way that is easy for usdr admins to export a zip file of all historic input files for a partner.
  • Partners want an easy way to export all upload files that were used in the treasury report (i.e. the final file per quarter per project)
  • Partners do NOT want an export of all upload files
  • Future user story could be created for allowing partners to export their own historic input files themselves.
  • This work will improve how files are stored, which is foundational work for future work around storing audit reports and treasury reports in the future, but initial focus is on input files only. However, audit reports and treasury reports aren't currently stored so there will likely be other questions/considerations for that work.
  • Once they start getting audit requests, it will be extremely helpful to be able to bulk download the files themselves. However, could be mitigated by USDR providing regular zip each quarter before this is ready

Outstanding Questions for Partners

  • Any concerns about all input files included (and not just final round per quarter)? OH only needs final; waiting to hear from RI
  • When do partners expect to need a full export for auditing or other purposes? Could it be at any time? --- don't need to pull in bulk yet, current address audit request by going in and manually pulling upload files as needed
  • are there any scenarios other than audits where you would want a full zip of all input files? record retention

Action Plan

  • Initial design drafted
  • Initial acceptance criteria drafted
  • High level technical approach & feature flag use determined
  • Designs & Acceptance criteria finalized
  • Eng task breakout complete
  • Assessment of whether partner training & communication actions are needed
  • Acceptance criteria testing completed & passed in staging
  • Feature flags enabled in production

Engineering Tasks

Acceptance Criteria

@ClaireValdivia
Copy link
Contributor Author

@as1729 per our conversation yesterday, created this user story for the the file migration work. please edit as needed! I think area where content is needed is clarifying acceptance criteria here (i.e. where will export button display and details on how the file export will work - i.e. zip file? correct that this will be done on an org by org basis?)

@ClaireValdivia
Copy link
Contributor Author

@as1729 FYI that I'm closing this out as it's now a duplicate of #3803

@github-project-automation github-project-automation bot moved this from 📋 Scoping to ✅ Staging in Grants Team Agile Planning Jan 14, 2025
@ClaireValdivia ClaireValdivia moved this from ✅ Staging to 🚢 Completed in Grants Team Agile Planning Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

2 participants