RT/CSCF/MFCF

October 25 2016

Attendees: Jennifer, Lawrence, Daniel, Fraser, Jeff,Lisa, Jim, Lori.

Notes from Lisa. Comments in italics by Daniel.

Action items

  1. MFCF/CSCF staff:
    1. experiment with RT 4.4 and create a list of questions relating to critical factors and features to bring to Nov meeting
      1. Do we have questions for them to bring to Best Practical?
      2. dev has full copy of data as of October
      3. email sending is DISABLED
      4. IST is happy to adjust permissions, turn on plugins, for us to experiment with
    2. Reach out to Lisa/Jeff if questions over next month
    3. Lisa
      1. Done:Send this to the team
      2. Planning
        1. IST project intake (done)
        2. Charter
        3. comm plan
        4. wbs
        5. roles and resp
        6. Other
  2. Done: Schedule a separate meeting to discuss IST/UW RT workflow and specs for new queues and what done when new queues/forms created - directly following Nov 22 Meeting
  3. Planning
    1. Monthly meetings and action items
    2. Fall/Winter planning, testing
    3. Training: RT 4.4. training from Best Practical
      1. Dates: Do these work for all?
        1. Jan 18 training (larger group of 12): Robyn, Lori, Daniel, Fraser
        2. Jan 19 consulting (smaller group of 8) Robyn, Daniel or Fraser
      2. Plan who to attend and date options (there will be room for 1-2 people from CSCF and MFCF to attend)
  4. ~May go live
  5. Review: https://cs.uwaterloo.ca/twiki/view/CF/STToRTInvestigation#Implementation_Plan
  6. RT4.4 overview
    1. On dev machine: rt44-dev.uwaterloo.ca
    2. Who would like to meet to go over standard workflow in RT 4.2 ?
      1. Daniel, Lawrence, Fraser, Jim- all?

Going through our list of Critical Factors with Lisa...

IST access to our queues beyond requests? Security group... who else?

custom fields: can have permissions of visibility
private items: they suggest a private queue to avoid searching by outsiders and co-ops (eg., helpdesk can’t see them)

moving things into queues: if you have access to both, can directly move. if you only have one, move it to general, add comment to move it to the other.

RT can’t do wildcard queue search- discussion about if Best Practical can add.
We can make custom dashboard search that includes all of our queues.

Bring questions to november meeting: how to do things we have identified.

4.4 going live before May; training for requesters when? MFCF will want training. Documentation for requesters is already online
https://uwaterloo.ca/request-tracking-system/new-rt4/requestor-documentation


Multiple queues for MFCF? discussion for them later.

IST can create forms (and templates) for us and show how they are implemented.

do we need our own group "service updates" (prominant at top of page)? if so, IST needs additional work to implement showing by group.
* wishlist item: group-specific alerts. (can instead be a dashboard)
* We could use a specific new queue to do it the same way they did

time management: 4.4 has new features; including a popup timer.

“aliases” can rename columns.
workflows meeting: just after next RT planning meeting.
Feature being worked on; auto-change status from “new” to “open” - otherwise it’s kept “new”. 4.4 makes it possible to enforce rules.

What information does IST gather when opening a ticket? (for next month).

4.4 can have custom roles (eg., responsible).

-- DanielAllen - 2016-11-07

Topic revision: r2 - 2016-11-21 - 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