Deadline Postmortem. We discussed various issues that were summarized by LorantSjouwerman offline.
Use chat (e.g., mattermost) instead of email to debug problems: There was a mixed response. Some felt this would work well for emergencies. There were concerns, however, that this would be a distraction and that important decisions should be via email and documented in JIRA. We could try this next semester as a trial run and see how it goes. We did confirm that history is preserved in mattermost and slack.
Large number of proposal corrections by staff after the deadline: Most felt that there were more fixes than previous semesters and that this was exacerbated by problems in withdrawing proposals. All but one of these fixes was near the deadline, however, and in the past we have allowed changes to the proposal before the grace period. The disappearing withdraw button is a known problem that has been investigated in the past with significant effort, but we were unable to reproduce the problem. We did not have major server load problems, but we had multiple isssues which may point to somethings more fundamental.
Problems printing propsoals with long source lists: There was one proposal in particular with many sources where the scientific justification would not be included in the PDF. Not clear if this is related to the large number of sources or not. MarkClaussen will create a JIRA ticket. DanaBalser will provide the merged PDF that includes a SJ to the SRP chair.
Validation messages for VLBA resources: We have seen this problem in the past whereby a valid validation error will stimulate a false error. The problem this time was slightly different as the "errors" where treated as warning messages and the proposal could be submitted. RickLively has identified issues in the code and will create a JIRA ticket.
Problem uploading Large scientific justifications:RickLively reported that there probably is a limit but on the database side. He will create a JIRA ticket. We should be able to flag these cases and provide a useful message. If so we should include this in the documentation.
Technical justification text disappearing: We have had problem with the technical justification page in the past whereby the user cannot save text. Here all of the TJ text for all fields disappeared. This may be difficult to reproduce but MarkClaussen will create a JIRA ticket.
Proposal has a null value in the Present field: This only causes problems in the PBT and is a known issue that is being mitgated.
PST/PHT Review Tickets Status. RickLively released several tickets on Friday. There are a few PHT tickets that remain, but we agreed to put these on lower priority to try to resolve some of the more serious problems discussed above (and below); these may take significant effort and we may need more time than that allocated for 22A.
Release Proposals for Review. There were significant problems with the techncial review assignments that caused a delay in the release of proposals. We agreed that we first need to be able to reproduce the problem and can simulate this on webtest. RickLively will create a JIRA ticket. MarkClaussen noted that the order of the techncial assignment may be important.