- Date: //date
- Time: 9:00 ET
- Location: nraozoom04
- Sprint Calendar
Agenda:
- v0.1 RIDs
- Follow-ups from Slack
- "Authors, we were instructed to save their names separately from any authentication system we might retrieve them from, so that those names always reflected the relevant users’ names at the time they became an Author for a particular Proposal. should the same be true for ScienceReviewers, or reviewers in general for the SRP Process?"
- timestamp could be end of configuration or end of review certification
- "Authors, we were instructed to save their names separately from any authentication system we might retrieve them from, so that those names always reflected the relevant users’ names at the time they became an Author for a particular Proposal. should the same be true for ScienceReviewers, or reviewers in general for the SRP Process?"
Open Actions:
| Description | Due date | Assignee | Task appears on |
|---|---|---|---|
| 2024-06-28 TTA Requirements Meeting | ||
| Jeff Kern | 2023-04-28 TTA Requirements Meeting | |
| 2022-09-02 TTA Requirements Meeting | ||
| 2021-12-17 TTA Requirements Meeting |
- New stories on Jira to prepare for Sprint 44
- Should there be a master science category table that is referenced at solicitation
- option 1 - No, SC are completely set at solicitation configuration and there is no checking to see if they are correct, also to pull information for metrics need to know all the SC ever used
- option 2 - Yes, but SC are not completely set at solicitation configuration so will have to update the master table if changes occur. Maybe need an interface to allow tta member to do so without involving devs
- option 2; will make a story for the interface to be added to solicitation configuration to edit the master list – STT-1084
- option 2; will make a story for the interface to be added to solicitation configuration to edit the master list – STT-1084