/build/static/layout/Breadcrumb_cap_w.png

Due Date Offset not sticking in Process ticket Setup

I've got the due date enabled, and I want the parent ticket to have a due date offset of 1 week, and the child tickets to have due date offsets of 2 days.  Whenever I use the drop down and select a due date offset and click save, it refreshes the screen and my due date offset is back to being blank.

 

I want to force it but the UI is being unkind :(  Silly to offer such a thing..... but... doesn't... work?


0 Comments   [ + ] Show comments

Answers (2)

Answer Summary:
Posted by: nshah 11 years ago
Red Belt
0

I think that might be an template issue. I tried it out on my box and the due dates didn't stick as well. I created the process, and actually ran it and the due date field didn't change. This may need to be reported to KACE as bug issue. 

Posted by: Wildwolfay 11 years ago
Red Belt
0

I've contacted KACE regarding this issue.

 

A quickfix in the meantime was to write my due_date_offset directly into the database using a change query ticket rule.

 

 UPDATE HD_SERVICE_TICKET
SET HD_SERVICE_TICKET.DUE_DATE_OFFSET = 2
where IS_PARENT = '0'

You can adjust the where statement as needed (Since I just use 1 process, my parent is 7, for 7 days, and my child tickets (above) are 2 days offset.)

 

Once they are written directly into that database table, if you try to modify them using the UI you will get the same results as attempting to modify them before, 0 change.  This seems to be a good temp fix for anyone that would like to use this feature.

 

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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