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

Epic 5: Activity Reports in MVP #8

Open
pamlo412 opened this issue Aug 7, 2020 · 1 comment
Open

Epic 5: Activity Reports in MVP #8

pamlo412 opened this issue Aug 7, 2020 · 1 comment
Labels
epic V1.0 MVP Indicates the release version for the issue

Comments

@pamlo412
Copy link
Contributor

pamlo412 commented Aug 7, 2020

Epic user story:
As a Regional TTA or Program Specialist, I want to create and edit activity reports with more standardized structures and a more central location so that there is broader awareness and understanding of my own and other specialists' activities, which awareness will in turn enable a more productive sharing and learning from one another so that we can improve the TTA services we provide and ensure the success of Head Start grantees.

This epic user story is deliberately general. More specific user stories live in the user stories under this epic.

MVP scope:

Out of MVP scope:

  • UX-motivated filtering of other fields based on role (exceptions are listed in the in-scope section)
  • reporting on multiple TTA activities in one report; a report may mention multiple events but they all add up to one TTA activity
  • selecting from goal objectives entered in the Grantee TTA Plan Smartsheet. With the work under Epic 6 Epic 6: Import SmartSheet data into the Smart Hub #37, we will get activity objectives into the Smart Hub. We have research to do before deciding how to handle goal objectives.
  • documenting each day of a several-day activity separately in the report. They can either write out mention of each day in the narrative or we can train them on when to start a separate activity report.
  • seeing actual revisions (e.g. “track changes”) entered by collaborators. (We do want to see revision requests for a submitted report that is rejected, but the changes made to drafts by collaborators prior to submitting for approval need not be called out in any way.)
  • assign each goal an ID Assigning IDs to goals  #151

Work included in this epic:
In epic 5 Issue is a child in the indicated parent epic

@pamlo412 pamlo412 added the epic label Aug 13, 2020
@pamlo412 pamlo412 changed the title Epic: Activity Reports in MVP Epic 3: Activity Reports in MVP Aug 20, 2020
rahearn pushed a commit that referenced this issue Aug 21, 2020
* Clarify package.json scripts

The backend `test` and `lint` commands now only test/lint a single
componenet. This should help clarify how to run tests or the linter
only the frontend or backend. Add readme for the frontend.

* Unit test result files go to the correct dir

* Remove unneeded env variables from compose file

* Remove the audit command

* Add cross-env as a dev package

This package allows cross platform setting of environment variables

* Update readme

Add section instructing to not switch between docker and host yarn
commands without installing proper dependencies. Add section that offers
help running docker on windows

* Remove build files, add to gitignore

* Clarify and update .env. Rename test

 * .env handling updated. .env is now .gitignored and the old .env
renamed to .env.example. Should make understanding it's purpose a little
easier. Added more to the comment explaining the .env files purpose
 * Test name now easier to understand for non-tech people

* Format lint:CI to console and file

Co-authored-by: Sarah-Jaine Szekeresh <[email protected]>
@pamlo412 pamlo412 changed the title Epic 3: Activity Reports in MVP Epic 5: Activity Reports in MVP Sep 7, 2020
@pamlo412 pamlo412 changed the title Epic 5: Activity Reports in MVP Epic 4: Activity Reports in MVP Sep 7, 2020
@pamlo412 pamlo412 changed the title Epic 4: Activity Reports in MVP Epic 5: Activity Reports in MVP Sep 8, 2020
@pamlo412 pamlo412 modified the milestone: V1.0 MVP Oct 30, 2020
@pamlo412 pamlo412 added the V1.0 MVP Indicates the release version for the issue label Oct 31, 2020
@pamlo412
Copy link
Contributor Author

pamlo412 commented Nov 9, 2020

Updated epic with decisions made at Product Planning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic V1.0 MVP Indicates the release version for the issue
Projects
None yet
Development

No branches or pull requests

1 participant