Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Agenda:

No meeting until 4/14

  • should there be further validation on the ISR scores at Finalization?
    • e.g., the scores cannot be identical.
  • "In the weeds" on Consensus Reviews 
    Jira
    serverDMS JIRA
    columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
    keySTT-913
    • Only Primary and Secondary SRP members can use Complete button
      • Blank -> Saved; Blank -> Completed (Save & Completed)
      • Edit widget is not available for SRP member once Review State Completed
    • Only Primary and Secondary SRP members can enter Consensus Comments except in Completed or Finalized Review States.
    • Once marked Completed, primary and secondary SRP members are locked out of CSR.
    • SRP Chair can edit Consensus Comments at any state except Finalized if not conflicted on that proposal
    • SRP Chair can mark complete if not conflicted on that proposal
    • If SRP Chair edits when the CSR is in a Completed state, the CSR stays in the Completed State (Complete button acts as save in this case)
    • SRP Chair can only Finalize when all Consensus Comments are Completed.
    • TTA member can edit CSRs, mark complete, and finalize all CSRs if needed
  • pending a change request....
    • starting in 24A, for VLA and VLBA are not all doing feasibility reviews
    • the criteria TBD but done during ISR sub-phase
      • Large, Triggered, ...
    • want to also do feasibility reviews after Consensus (e.g., first quartile proposals)
    • GBT is doing feasibility reviews for all

Open Actions:

Task report
pages68321335