CSCF Staff Meeting Presentation 2017-03-24

  • This is a followup to last month's presentation.
  • Questions noted:
    • Q: When should we start using RT? A: as of the first training (unless you're an alpha-tester).
    • Q: What about clients who don't want an email upon ticket creation/closing? A: we could change it per-queue to not do that; or implement something fairly customized; but current workaround is: create the item with you as requester, then change the requester to the client; then change the requester back to you before closing; then change the requester back to them for searches/reporting. (Ugh). Daniel will follow up with Lori.
    • Q: Will we have the ability to request changes to our workflow and queues after May 1? A: Yes; they're motivated to getting us on the same system.
    • Q: Will we get shared saved-searches? A: yes. Implementation details TBD in April.
      • A very common search is: student visits and we want to get all items related to them by their userid; and display all their items chronologically backward.
        • This is actually built in to RT: top-menu "Search" -> "Users" -> fill in and search -> displays the results.
    • Q: How about other searches where we just want to change one parameter? The saved-searches don't seem to do this.
      • A: We could have an external page, a la the runon sentence. To be worked on after May 1. How would this be implemented?
        • Experimenting shows that a Simple Search result becomes a URL that can be tweaked. Here's one that reports all of Requester ENDSWITH (caution; it's long):

Start Presentation

Slide 1: ST->RT Project Update

  • As of March 24
  • 1 month to go!

Slide 2: Update Highlights

  • We have requested our queues to be set up in RT by the end of next week.
  • We have been given access to some IST Queues: -General-, all five of the IST Client Services queues
    • and hopefully Networking Services, once Lisa gets permission
  • We have requested two custom roles that will be available when IST upgrades RT from 4.2 to 4.4 on April 22
    • Supporters: aka "additional owners" who are doing work
    • Accountable: aka ST's "Responsible": optional; such as for point-of-contact who isn't the manager for the queue.

Slide 3: Client Communication in Early April

  • We will come up with communication plans for our clients
    • Including "you will receive automatic email when a ticket is created, and when it is closed."
    • (An implication of this: dependencies should have the requester set to you, unless the client actually wants to know when the dependency is done.)
  • As of now, we will NOT give clients a survey on completion, but our managers are discussing and we will probably start asking useful survey questions, next term.

Slide 4: Training

  • April 12, 10:30-12:30 mandatory session for CSCF and managers from MFCF (DC 1302)
    • Bring your laptop if you want to try things out
  • April 26, 10:30-12:30 Advanced Q&A session for CSCF

Slide 5: Decisions

  • Early usage?
    • Starting early in April, you can make RT updates in the production RT (including our custom fields)
    • For testing, there will be a URL for a test system you can make throwaway items in.
  • Late usage?
    • Management says: please don't make new ST items after the end-of-term (May 1).
    • Goal is <50 open ST items (that aren't "uncommitted")

Slide 6: Questions?

-- DanielAllen - 2017-03-23

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