Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot close out ticket on same date as due date

Max Larsen February 5, 2021

My team is finding that the Due Dates fields are causing some issues when closing a ticket.

****For example, if a ticket has a due date of today, and they go to close a ticket today, the workflow is preventing them from closing the ticket until they move the due date out by one day.****

For example, if my ticket has a due date of 2/2/2021, and I try to close it on 2/2/2021, it will error out and require me to change the due date to 2/3/2021. 

Any assistance is much appreciated. 

1 answer

1 accepted

0 votes
Answer accepted
Kian Stack Mumo Systems
Community Champion
February 5, 2021

@Max Larsen,


When you say that it's preventing them, what do you mean? An error is thrown during the transition?

That sounds like a workflow validator was set up to prevent people from closing if the due date has already passed.. I'd check the workflow and see if you can take that validator out.

Thanks,

Kian

Max Larsen February 17, 2021

@Kian Stack Mumo Systems Thank you! I've gotten there, but unfortunately when trying to move the workflow. The time stamp is saying "Due date isn't greater than or equal to (15/Feb/21 6:33 PM)," It is currently 1:33pm. 

 

For some reason that time stamp is 5 hours ahead. Any guidance with that?

 

Thank you again

Kian Stack Mumo Systems
Community Champion
February 17, 2021

Check your default timezone settings?

Underneath Settings > General Configuration you can see what that is.

 

Screen Shot 2021-02-17 at 12.50.44 PM.png

Like Max Larsen likes this
Max Larsen February 17, 2021

@Kian Stack Mumo Systems 

Right, have done that. It's in New York time (located on east coast). That doesn't seem to be the problem for some reason

Max Larsen February 17, 2021

IMG_8929.jpeg

Kian Stack Mumo Systems
Community Champion
February 17, 2021

I was able to replicate your issue. I couldn't figure out how to update the date/time to be in my timezone, but I was able to figure out how to get past the issue.

Try checking the box to "Include time part" in your validator.

 

Screen Shot 2021-02-17 at 2.02.08 PM.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events