Skip to main content

Modify Slate Recurring Tasks Googledoc

Purpose

The purpose of the Google Sheet is to help visualize the teams lulls and peaks throughout the year with all the processes we have in place. Being able to know something is upcoming and reach out to the user in advance should allow us to minimize last minute needs/changes, and also give us enough time to determine who the data owner is if someone has shifted positions, or left the university. The "Date Order" tab will take the data you add from the instructions below and sort by date, and make 1 row per department to easier work with users to see their departmental tasks upcoming. 

image.png

The google sheet can be found here: https://docs.google.com/spreadsheets/d/1Z4oEQmqFAK2nNyItj_wxqs-mcKqkP6wIYmm9bGP1RD0/edit#gid=0

Instructions
  • Click the "Tasks" tab on the sheet

    image.png

  • Set all the Columns in the Sheet:
    • Month (Required) - Choose the month this process happens. You can use the month you were made aware by the user that changes need to be made, or adjust it back a month if they were sending it to you last minute.
    • Day (Required) - Choose the Day Range. This is just to give us some insight if it needs to be completed in the beginning, middle or end of the month. 
    • Department 1 (Required) - Choose the primary department this task is for. 
      • Note: If the Department is missing, you can add it by going to the "Data" tab and adding it to the list under Column C (Department). This will automatically add it to the drop down. 

        image.png

    • Department 2 (Optional) - Choose an additional department that is involved in this process. If the process has mailings involved, ensure Marketing is added as a department, as we would like for them to review any messaging going out. 
    • Department 3 (Optional) - Choose an additional department that is involved in this process. If the process has mailings involved, ensure Marketing is added as a department, as we would like for them to review any messaging going out. 
    • Task (Required) - Give a title to the task
    • Notes (Optional) - Any notes that you might need listed here that might be separate than the documentation process
    • Documentation Link (Required) - Any task here should have documentation built out on the recurring task. After you build it, add the link here. To get a static link of the documentation, instead of using the URL, hover over any text on the documentation and a copy link will popup. Take out anything after and including the #. 

      image.png

    • Recurring Ticket Number (Required) - As this form is for recurring tasks, there should be a ticket created. Follow the instructions on how to create a Recurring Ticket in RT, and add the Ticket ID to this sheet. Instructions can be found here: https://bookstack.clarkson.edu/link/90