Best solution for a specific scenario?

[Dina Goncharenko]

Hello community, 

Here is my task. An auto mechanic needs to perform a serious of preventative maintenance tasks on different cars at certain intervals. For example, the oil must be changed every three months. The tires must be rotated every 6 months. And so on. However. The mechanic does not perform these tasks on a certain date throughout the year, e.g. change the oil - January 1st, April 1st,  July 1st, Oct. 1st...The mechanic can change the oil anywhere from 1 - 31 of January, which does not mean that the next oil change has to happen on April 1st. It has to happen 3 months after the date the oil was actually changed. Once the oil is changed, the original ticket is closed. The new ticket should be cloned from the original ticket and auto-scheduled. It's created date should be 3 (or 6, or 9 - depending on the task) months from the date the parent ticket was closed. 

As a community, I am hoping we can collectively come up with the best solution for this task. Any thoughts and ideas are very appreciated and welcome!

Thank you!

Dina

[Craig Castle-Mead]

Hey Dina,

Delaying the created date would likely mean more complicated logic. My thinking is leaning towards an issue tyoenfor each of the maintenance tasks (or anmaintenance issue type with a custom field for the type of task if there’s lots), and based on the close date of one task (is: oil Change) use some scripting to create the next maintenance task and set the due date of that issue to be close date + time period (3/6/9 months etc).

you could then JQL for tasks that are overdue, or due in XX days and still To Do status (or similar) and dashboard/subscribe to this filter as an action list. 

With a custom field or parent issue for the customer, you could even get some scripting to email the owner saying your oil change is due, please call us to book a service

CCM

[Dina Goncharenko]

Thank you, Craig. Could you advise on the add-ons to use for scripting and JQL? JQL will have to run daily.