Versions Compared

Old Version 1

changes.mady.by.user Tyler Johnson

Saved on

compared with

New Version 2

changes.mady.by.user Tyler Johnson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Summary: A short, descriptive title that summarizes the issue or feature request that you would like to make. 
  • Priority: The level of importance of the issue. The values are described below: 
    • Trivial: A problem/feature with little or no impact on operations. E.g. small typos on screens, etc.
    • Minor: A low priority feature or fix, or a long-term request made as part of operations planning. 
    • Major: A medium priority feature or fix, or a medium-term request made as part of operations planning. 
    • Critical: A high priority feature or fix that will drastically improve operations. May or may not need immediate attention. 
    • Blocker: An experiment-breaking problem or missing feature. Requires immediate attention.
  • Component: The sub-system or area of the facility that is affected. This helps direct the ticket to the correct person more quickly. You may include more than one component in your ticket as needed. 
    • TMO/RIX/TXI/XPP/XCS/MFX/CXI/MEC/UED: Use for hutch-specific issues, including experiment setup/planning. 
    • DAQ: Use for DAQ related issues, e.g. DAQ bugs or psana, not DAQ setup in the hutch.
    • Laser: For laser controls issues, not related to hutch controls.
    • Timing: For Event and Precision timing issues. 
    • Analysis Tools: For data analysis tool issues, e.g. smalldata.
    • IT: For issues related to IT infrastructure, e.g. servers, network, new control machines, etc. 
    • Beam Delivery: For issues related to beam delivery
    • Common: For common issues that may affect more than one area/instrument. 
    • Hutch Python: For issues related to the hutch python environments provided at LCLS.
    • SED: For issues related to sample delivery or the SED department.
    • Beam Delivery/XBD: For issues related to beam delivery through the FEE/EBD to the hutches.
  • Description: A text description of the request or fix. Add as many details as possible at the time of submission. 
  • Attachments: A place to provide screenshots, spreadsheets, or other documentation that can help in the completion of the ticket.  
  • Name: Your name. 
  • Email: Your SLAC email.

...

Info

This form does not currently provide a field for including deadline information. Please include the desired timeline for the fix/feature as a part of your description. 


as far as I'm concerned I need a decent title & description of the problem (check that you don't accidentally put that in the environment box which happens to come first). I'm asking to please assign a component (of the existing ones, so let the scientists know what that would be) so that you don't have to wait for me to look through tickets. We can put everything else in, I'd rather get mediocre tickets than no tickets.
As far as priority or due date: some information about when something is needed helps, but in the hutches I would typically ask the instrument lead to manage the priorities together with the POC.