/build/static/layout/Breadcrumb_cap_w.png

New Ticket - Notify All Owners

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 Custom Ticket Rule may be used to send a notification email to all users within the owners label of the queue a ticket is created in.

1. Select your queue 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. Use the SQL select statement below.  You may use the '$' variables in your email.

select
HD_TICKET.ID,
HD_TICKET.ID ticket_number, -- $ticket_number
HD_TICKET.TITLE ticket_title, -- $ticket_title
SUBMITTER.FULL_NAME ticket_submitter_name, -- $ticket_submitter_name
SUBMITTER.EMAIL ticket_submitter_email, -- $ticket_submitter_email
CAT.NAME ticket_category, -- $ticket_category
IMPACT.NAME ticket_impact, -- $ticket_impact
PRIORITY.NAME ticket_priority, -- $ticket_priority
STATUS.NAME ticket_status, -- $ticket_status
group_concat(OWNERS.EMAIL) as EMAILCOLUMN
from
HD_TICKET
join HD_TICKET_CHANGE C on HD_TICKET.ID = C.HD_TICKET_ID
and C.ID = <CHANGE_ID>
left join USER SUBMITTER on HD_TICKET.SUBMITTER_ID = SUBMITTER.ID
left join HD_CATEGORY CAT on HD_TICKET.HD_CATEGORY_ID = CAT.ID
left join HD_IMPACT IMPACT on HD_TICKET.HD_IMPACT_ID = IMPACT.ID
left join HD_PRIORITY PRIORITY on HD_TICKET.HD_PRIORITY_ID = PRIORITY.ID
left join HD_STATUS STATUS on HD_TICKET.HD_STATUS_ID = STATUS.ID
join HD_QUEUE_OWNER_LABEL_JT HDQOLJT on HD_TICKET.HD_QUEUE_ID = HDQOLJT.HD_QUEUE_ID
join USER_LABEL_JT ULJT on HDQOLJT.LABEL_ID = ULJT.LABEL_ID
join USER OWNERS on ULJT.USER_ID = OWNERS.ID
where
C.DESCRIPTION like '%Ticket Created%'

6. Place a check in the "Email each recipient in query results" check box and configure the email as follows:

    Your email subject line should include the following text to ensure replies to the email go to the existing ticket, rather than generating a new ticket:

[TICK:$ticket_number]
    For "Column containing email addresses:" enter: "EMAILCOLUMN" (without quotes).

    Sample email Message (note the highlighted kbox portion of the URL - this will need to be changed to your K1000 web server name.  Also be sure to change "http" to "https" if you are using SSL):
A new ticket has been added to the Service Desk.

Ticket number: $ticket_number
Title: $ticket_title
Submitter name: $ticket_submitter_name
Submitter email: $ticket_submitter_email
Category: $ticket_category
Impact: $ticket_impact
Priority: $ticket_priority
Status: $ticket_status

For complete details, see:
    http://kbox/adminui/ticket.php?ID=$ticket_number

7. The Frequency for this rule should be set to "on Ticket Save."

8. Click the "Save" button.


Comments

  • Hi, This worked great for me, thanks so much! Is there a way to also send a push notification to the iOS K1000 GO app when a new ticket is created? - BDEEN 9 years ago
  • Have you updated your system to 6.4 yet? If you have is this ticket rule still working for you? For me it will run and send an email but the email does not have any text where the variables output. - twalker5544 8 years ago
    • I'm seeing problems too. Has something changed? - caseyo4 8 years ago
      • I recreated this rule by copy and pasting from this article, and it still works as expected with no missing data (K1000 v6.4.120261). - PHKace 8 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