Page History

Attendance:

Agenda:

v0.1 RIDs
Jira
server DMS JIRA
jqlQuery filter=14704
serverId eb2e750b-a83a-387e-8345-36eee8a98f01
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

Task report

pages	68321335

for Sprint 45

Jira

server	DMS JIRA
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	key in (STT-1067, STT-1076, STT-1077, STT-1078)
serverId	eb2e750b-a83a-387e-8345-36eee8a98f01

STT-1076

STT-1077

STT-1078

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

Task reportpages68321335

- - option 2; will make a story for the interface to be added to solicitation configuration to edit the master list – STT-1084