Below is an extract from Lisa's notes. Directly preceded by STToRTInvestigationTechnical20170308 between Daniel and Jeff.

Lisa and Jennifer and Jeff were there; Robyn was there from MFCF; Daniel and Lawrence were there from CSCF.

Agenda

Go Live 4.4: April 22nd (Sat).

  • Lisa, Jeff, Jennifer are prepping for go-live on April 22nd.
  • on test machine: we agreed to do the following testing. Lisa shared testing instructions: https://sharepoint.uwaterloo.ca/sites/rt4/RT44Planning/UpgradePlanning/GoLiveRT4TestingMar-Apr2017.docx
    • coordinate testing for browsers and queues
      • Safari (robyn)
      • IE (Lawrence)
      • Chrome Linux (jeff)
      • Chrome windows (lisa)
      • Chrome mac (Daniel)
      • Edge (Lawrence)
      • Firefox Linux (robyn)
      • Firefox windows (Lawrence)
      • Firefox mac (Daniel)
      • android (jeff)
      • Iphone (Daniel)
      • BB (lisa )

Training Sessions:

  • April 12, 10:30-12:30 mandatory session for CSCF and MFCF Managers (Lawrence will book a room)
  • April 26, 10:30-12:30 Q&A session for CSCF (Lawrence will book room)

Review action items

  • pull time worked data from rt4.4: Daniel and Jeff discussed this morning; looks straightforward. Internal due-date: Daniel/Jeff to implement by March 20th.
  • additional list of items for Daniel to investigate and/or ask Jeff about: bring back to next meeting (Tuesday March 21).
  • CSCF to request queues and custom fields needed to be set up now in RT 4.2
    • CSCF-CSI, CSCF-RSG, CSCF-TOP ?
    • Info Lisa needs: name, edit access, email notifications, feedback on resolved requests, do we want reminders every wednesday? (ticket owners and queue owners), optional email alias name (we already get rt-queuename@rt.uwaterloo.ca)
  • optional: email template for auto-reply : find in dev: admin -> global -> templates -> search page for "Resolved"
    • later: bring up response survey and how we want to handle it.

  • MFCF to request queues and custom fields needed to be set up in RT 4.4 when necessary
  • MFCF/CSCF to discuss custom role requirements and bring to next meeting
    • "Supporters" and possibly also "Accountable" (which currently is assumed to be Queue Owner)
    • Discussion: best to offer these roles widely, if they are an improvement for all parties.

Change Requests

-- DanielAllen - 2017-03-07

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2017-03-09 - DanielAllen
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback