You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Due Date has always been optional on project, it was to allow users to update if request was long dated. There is little to no automation on project, especially nothing is in place concerning a due date. Time to resolution SLA is 2 business days; in settings, under time to resolution SLA, the Goal is 2 days. Recently the due date started populating 6-7 days from created date OR not populate at all. I thought the SLA was driving the due date but the Time to Resolution clock is still tracking items correctly. Any thoughts on what could be causing this? Am I supposed to have automation for the due date? How was it populating without automation?
You may want to check your Jira settings to see how many hours a working day has. Maybe this was adjusted so that 2 business days (I imagine this means 16 hours within your operation hours) is actually 6-7 days ahead because someone defined a work day as 2-3 hours or something?
Just a wild idea, have not tested this.
When you look at an example issue with this symptom, and check the change history, who/what does it indicate is setting the Due Date field? Looking at that may point you to the cause.
Unfortunately nothing. Initial thought was maybe requestors are picking 1 week out from created date but it's too consistent and coincidental that every request is now that way. Just looked at a new request and in history there is just the user name and "created issue 1 hour ago"
Have you talked to your site admin to learn if any scripting/addons might be doing this?