Versions Compared

Key

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

Agenda:

  • https://safe.nrao.edu/wiki/bin/view/Software/GbPhtDocs
  • Edge case
    • Benign:
      • SRP Chair has not assigned Review Types but SRP member has worked far ahead marked ISRs as Saved or Completed.
      • Jira
        showSummaryfalse
        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-879
        says that the Finalize button is available if all of the ISRs with Review Type not equal to None have Review States of Saved or Completed.
      • In this case, the SRP Member's ISRs are all Review Type = None so the Finalize button is available because technically the condition is satisfied. Finalizing does not change the Review States to Finalize so the SRP member will have to go back later and Finalize when the chair is done with assigning Review Types. This is acceptable. We assume the chair and srp members are in communication.
    • Potentially Troublesome:
      • SRP Chair is in the process of assigning Review Types (they have saved but are still working)
      • A SRP Member jumps the gun and hits Finalize and the ISRs with Review Types not equal to None have their Review States changed to Finalized. The SRP chair can no longer modify the Review Type of that SRP member. 
        Jira
        showSummaryfalse
        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-871
        The solution is that the TTA member will have the power to change the Review Type even if the state is Finalized. This will protect against this case.
    • Probably Benign:
      • Jira
        showSummaryfalse
        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-933
        says that the condition for initiating Consensus Review is that all the ISRs in a panel with a Review Type of P,S,T have Review States of Finalized.
      • Until the Chair assigns Review Types, all Review Types are None so the TTA member could immediately start Consensus. Of course, the TTA member never would do this in practice...

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-907

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-914

  •  When ready, we will do a mock review process at a friday meeting
  •  When we release v0.2 for an external group, we will plan to do it together on zoom to help the reviewers navigate the new system

Open Actions:

Task report
pages68321335