Planning and tracking recurring maintenance in JSD or Jira Software

Shannon_mkz717

I'd like to hear what others are doing to plan and track recurring maintenance activities. We have quarterly and monthly maintenance as well as more on-demand sort of patching activities. These are not customer generated asks and usually require a bit of planning and steps to complete (dev, test, prod). But they are standard in nature and recurring. 

We have both Jira Software and Jira Service Desk. How do you plan your recurring maintenance within either of these products and what are the pro's and con's? Any other advice is welcome! 

Mirek

Hi @Shannon ,

Well it depends on how much information you want to track. If you want to track that maintenance need to happen and do not care about the result you could simply have standard tickets that can be reopened each month/quarter.. This of course should be automated do reopen..

If you have more complex operations or things that you want to track you need to somehow create a new ticket.. Again, manual process is the starting point. Every month you create a ticket a and track the maintenance, but most of the power is done with Automation..

There are of course plugins out there on the Marketplace that can help you create recurring tasks and fire them automatically whenever you want.. That is probably the easiest (but might not be the cheapest if the plugin is not free) option.

Using REST API is free and giving also a lot of option to integrate this with servers, scripts directly so that tickets would be created automatically whenever then need to be created.. Possibilities here are endless.