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.

Sign up for GitHub

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

Jump to bottom

Basic Data Export #3067

Open
11 tasks
jonnalley opened this issue Nov 13, 2024 · 0 comments
Open
11 tasks

Basic Data Export #3067

jonnalley opened this issue Nov 13, 2024 · 0 comments
Labels
dev frontend ready Designers have created the designs, story has been refined, and ready for a Developer to begin story A defined user story adhering to expected norms including a narrative UX task UX-team related tasks and to-dos

Comments

@jonnalley
Copy link
Contributor

jonnalley commented Nov 13, 2024 •
edited by npage123
Loading

User Story

As an OPS System Admin, I want to access and download a data export of all attributes of relevant OPS entities so that I can perform obligatory actions on the data outside of OPS.

Acceptance Criteria

  • User can procure and download a set of all relevant entries in for a given set of concepts such as budget lines, contracts, projects, etc....
  • This export should only be accessible to user with the System Admin roles.

Tasks

  • Identify and prioritize all the places/OPS entities & data types that need to be exported (List of CANs, budget lines, agreements, and ?)
  • Design a way to trigger the export process

UX

Dev

Definition of Done Checklist

  • UI works as designed (UX team)
  • PR(s) have been merged to main
  • Design/tech debt eliminated
  • New design/tech debt documented (if applicable)
  • Build process updated
  • Documentation updated or added
  • Feature flags/toggles created

Additional Context & Resources

  • This might be necessary due to certain OPS features not being released yet. In example, getting data on contracts now since IAAs and AAs aren't ready
  • This would also be necessary to aggregate info from disparate system that OPS could not potentially do
  • Another reason might be to supplement additional information outside of OPS for common upstream data gathering.
@jonnalley jonnalley added draft draft only, not ready for prime time. still being authored or needs refinement story A defined user story adhering to expected norms including a narrative labels Nov 13, 2024
@jonnalley jonnalley mentioned this issue Nov 13, 2024
Closed
5 tasks
@jonnalley jonnalley added dev frontend ready Designers have created the designs, story has been refined, and ready for a Developer to begin and removed draft draft only, not ready for prime time. still being authored or needs refinement labels Feb 18, 2025
@npage123 npage123 added the UX task UX-team related tasks and to-dos label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dev frontend ready Designers have created the designs, story has been refined, and ready for a Developer to begin story A defined user story adhering to expected norms including a narrative UX task UX-team related tasks and to-dos
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonnalley @npage123