You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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.
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
@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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check your default timezone settings?
Underneath Settings > General Configuration you can see what that is.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.