Dev chore/task: Pull data from our database to populate fields implemented in UI before database was ready #90
Labels
Backend
Flag to indicate the story's focus
enhancement
New feature or request
In epic 5
Issue is a child in the indicated parent epic
V1.0 MVP
Indicates the release version for the issue
Comments
pamlo412
added
In epic 5
1 task
|
Closing this story as no longer needed because other stories are covering this need. See links to the other stories above. |
rahearn
pushed a commit
that referenced
this issue
Dec 17, 2020
* check if env vars can be referenced directly in deploy config * try as deployments vars, and out of the manifest * add back to manifest * was it proactively checking other branches? * check that we really need vars in manifest * try migrate as cf run-task in single command * ignore that failing fe test for now * omg, this takes forever * try wo explicit wait * add back sleep, up to 120; add db connect directions * move sequelize-cli to production deps * change migrations path to build dir * move production sequalizerc to file * update migration command * add back all the jobs * rename prod sequalize config * missing ' * don't restart app Co-authored-by: Sarah-Jaine Szekeresh <[email protected]>
rahearn
added a commit
that referenced
this issue
Dec 17, 2020
* adhoc-main: CD: Run database migrations (#90)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Task description:
This chore/task will replace UI-coded values with values pulled from our database. This work is needed for fields implemented before #23 was done.
Acceptance criteria:
The following fields pull the correct values from the database instead of fake values in the UI:
Grantee Namehandled via Display Grantee Names and Grant Numbers pulled from database #163Grant IDalso handled via Display Grantee Names and Grant Numbers pulled from database #163Non-Grantee Namehandled via Display non-grantee options pulled from database #164TTA Smart Hub users (for the collaborator field) - note that work to implement this field may include filtering and may warrant a separate storyAdd collaborators to draft Activity Reports #109ReasonCapture reasons for a TTA activity #171TopicsSelecting Topics from a list filtered by role #161Participants involved in grantee activitiesEnable entry of grantee participants #172Participants involved in non-grantee activities (different than the preceding list)Enable entry of grantee participants #172The text was updated successfully, but these errors were encountered: