/build/static/layout/Breadcrumb_cap_w.png

Scheduling Ticket Creation

The instructions on this page are provided "as-is," without any express or implied warranty. In no event shall the author, or Dell be held liable for any damages arising from the use of the information provided on this page.

WARNING: Always review "Precautions when creating ticket rules" before writing any rules.
*Created on K1000 v6.2.109329.
This method for auto-creating tickets on a regular / scheduled / recurring basis requires creating a Custom Ticket Rule in a second queue (we'll call "Q2") to send an email to the queue we want the ticket created in (we'll call "Q1").  This is due to a previous K1000 update that restricts a Service Desk queue from emailing itself.

The email address you've configured for Q2 will need to be a valid submitter for Q1.
Pick one of the options below to make Q2 a valid submitter in Q1:
  • Option 1: Set Q1 to "Allow all users as submitters" and "Accept email from unknown users"
        oJdzWV.png
  • Option 2: Create a new user with Q2's email address.  This removes the need to "Accept email from unknown users"
        vSS9IX.png
  • Option 3: Create a new user with Q2's email address AND add that user to your submitter label for Q1.  This removes the need to check "Accept email from unknown users" and "Allow all users as submitters."
        0ytpDz.png
Now that Q2 is allowed to submit tickets to Q1, we'll configure the Custom Ticket Rule to send an email to create the ticket.  This rule must be created in Q2.

  1. Select Q2 from Service Desk > Configuration > Queues
  2. Scroll to the bottom of the page and click [Customize] next to "Custom Ticket Rules"
  3. Select Choose Action > New (SQL)
  4. Set the Name and Description (optional) as you like
  5. Copy the SQL below to the "Select SQL" box and replace "servicedesk" with the first part of Q1's Email Address (NOT the first part of Alternate Email Address) - the part of the Email Address before "@":
    Queue Email Address for reference, continue below for SQL query:

    SQL query and screenshot:
    select
    "servicedesk" as EMAILCOLUMN


  6. Check "Email each recipient in query result" and make sure no other boxes are checked except "Enabled"
  7. Enter a Subject for the email - this will become the Title for the generated ticket
  8. For "Column containing email addresses:" enter: "EMAILCOLUMN" (without quotes)
  9. For "Message:" the first line must be "@submitter=unassigned" to remove Q2 as the submitter of the ticket and avoid an email loop between the two queues.  The lines after the first will be added as the first comment of the generated ticket.  Here is a sample email:
    @submitter=unassigned
    This will be the initial comment on the created ticket.

    This line will also be included in the initial comment on the created ticket as well as all lines following this one.


  10. Set the Frequency and Next Run to define how often, and when to create the recurring ticket (DO NOT select 'On Ticket save' or a new ticket will be created every time any change is made to any ticket! ).
  11. Click the   Save   button.

You may now go back in to the rule you just created to click the   Run Now   button to test.


Comments

  • While not being ideal, this does work. However, you cannot use custom schedules using the Ticket Rules, so no Quarterly or Bi-Annual tickets. - Ryft_IT 8 years ago
    • Realizing this is 2 years old: I use these as quarterly tasks. I built my automated tickets using roughly the information above. But I added the schedule to the select statement to run quarterly.

      select
      "servicedesk" as EMAILCOLUMN
      from
      (select 1) T
      where
      monthname(now()) in ("January", "April", "July", "October") - Cochesdiez01 5 years ago
      • This is exactly what I'm looking for but I also need a statement for yearly and every 85 days (it needs to be ran a little early to give us a few days in advanced.) - abratton 5 years ago
  • This works great for our recurring tasks that need to be tracked. I also set additional ticket attributes using the @ variables. - jpack1221 5 years ago
    • How did you get this to work? I am trying to assign the ticket to a technician using @owner=username and it didn't work. - abratton 5 years ago
  • I listed the actual username. For example:
    @submitter=Doe, John
    @owner=Doe, Jane
    @impact=Task oriented
    @priority=Non-urgent issue <40 hrs
    @status=Assigned
    @category=support team - jpack1221 5 years ago
This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ