Setting dynamic due dates has issues

[Amir Vegdani]

Setting dynamic (advance) due dates is not working properly.

In case of monthly ticket, when the ticket is created one month in advance JIRA always considers 1 month = 31 days

For e.g. if the ticket is triggered on 5th Oct 2017 and dynamic due date is set after one month. The due date on the new ticket will be 05th Nov 2017.

However when the same ticket is created on 5th Nov 2017, the due date will be 6th Dec 2017 as November only has 30 days.

[Łukasz Modzelewski]

Hi Amir,

As you noticed JIRA considers 1 month = 31 days, in dynamic due dates we are currently counting on build in functionalities, you could try to use 30d instead to make sure the due date have the same period for each ticket.

We are thinking about adding support for other periods like end of the month, so each ticket could have due date restricted to end of the month it was created.

In order to implement this we would need to create our custom way of counting dynamic dates, it is not impossible but it will have to wait, as we are currently working on adding support for interval triggers e.g. 2 weeks periods.

You can check out our Roadmap, to see what is coming up next: The Scheduler for JIRA Server Roadmap

I will reopen this ticket when the times come.

Best regards,

Łukasz Modzelewski