Biweekly Trainer's Meeting Agenda & Notes 04-06-11

Agenda/Notes:

Send email to jmjohnstone@ucdavis.edu know if you'll need to dial in and I'll set up the Toll-free ReadyTalk line: 866-740-1260, access code 7545991

Attendees: Joyce, Steve, Dave, Fernando

Topics

1. Testing for Sakai 2.7.2
     a. April 8 is due date for 2.7.2 TEST - Steve/Fernando can test next week if it's ready.

2. Training schedule issues

     a. for Steve - do workshops on Tuesday
     b. for Fernando - one workshop a week and three drop-ins; and then one-on-ones as needed.
     c. Start of Quarter issues - Kirk found  a bug (SS-308) people can be added as guests using their UCD emails if the lookup process failed
     d. Larger vision for training and support as user experience evolves - Joyce sent email to Liz to see how to go forward on this (6/29 no response and Liz left May 2011)

2. Remedy or RSN Ticket Status
     a. Problem Statement for Letter Grades - GRBK-853 and GRBK-890 - not needed this is now part of GB2 QA Code review
     b. Steve focus on Pending and Work In Progress tickets instead of assigned.

3. SmartSite Support Plan - see project plans
   Need to communicate to customer when issue is being escalated - need canned response for this - Add to T&R agenda and discuss.

4. Communication Tasks
    a. TSP Qtrly Meeting 4/14 - upgrades & downtime; Steve will do this and we will meet to plan communications.
    b. See Jira Tickets below - Joyce changed blockers to critical
    c. Fernando - SS-276; posted comment Fernando will review document and have Kirk post.

Past Action Items:

  1. Continue to clean up Jira tickets.
  2. Posted changes to CMDCOM-11 on 10/14 for Middleware to complete these changes: due from Middleware Feb 2011.
  3. Posted another comment (on 2/22) to Kirk SAK-549 - Kirk to see if this was still planned:  Where is the request for stuID in roster and pictures?

Real-time list of Blocker & Critical tickets for next production release

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.