Page History

• Date: //date
• Time: 9:00 ET
• Location: nraozoom04 
• Sprint Calendar

Attendance:

• Jeff Kern
• Dana Balser
• Mark Whitehead 
• Allison Costa
• Mark Ferguson 

Agenda:

• Confirm Conflict Certification (SRP Member action and TTA Group member powers;

  Jira
  showSummary false 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 serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-1146

  )
  

  • For a SRP member, they would not have a “save” option on conflict certification. They can only certify or the changes do not persist.

  • 
    

    A TTA member should be able to change a conflict designation at any time. We do not need the software to manage if it is the result of the auto conflict process or a user specified conflict, as we trust the TTA member.

  • A TTA member should be able to certify a user's conflict status, if necessary.
• Mark F -
  • https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/
• Allie -
  • Mapping Requirements to Jira Stories
  • 
  • 
  • 
  • 688-TTAT-014-MGMT_REQ-Mapped-Jira-1-20-23.csv
• From Backlog 1/23/23
  • Confirmed removing "Closed" as a Review State in favor of just deleting the ISR.
  • Confirmed removing "None" as a Review Type
  • ISRs are created upon the assignment of a Review Type (Primary, Secondary, Tertiary)
  • If the Review Type is unassigned, then the ISR is deleted.
  • A SRP Chair or TTA member has the ability to change the Review Type.
    • If the Review State is not blank, then a warning is given saying that data (ISR) will be deleted
    • If the Review State is Finalized, then the Review Type cannot be changed by either TTA or SRP Chair.
• Discussion on stories in Sprint 47
  • As written, are these capturing where (e.g., FE/BE) and what (e.g., requirements) the work currently is?

Open Actions: