I need assistance setting up two recurring maintenance tickets in our system: Small Generator – Ple

[Gabriela - LeanZero]

JSM doesn't have a native recurring-ticket feature, so the way people handle this is a scheduled automation rule. One rule per cadence.

Go to Project settings > Automation > Create rule, pick the Scheduled trigger, and set how often it fires. There's a simple rate ("every 4 weeks") or a cron expression if you need something like the first Monday of the month. Then add a Create work item action and set the request type, summary, and whatever fields belong on the maintenance ticket. Your two generators are on different schedules, so that's two rules, one each.

If you paste the two cadences you're after (say small generator monthly, large one quarterly), I'll give you the exact schedule setup for each.

[Dorota Popowska - Vilisoft]

Hi @Mark Revely,

Another option is Clone Expert for Jira with its Scheduler feature.

You can use each maintenance ticket as a template and schedule it to be cloned automatically according to its own recurrence, date, time, and time zone. The scheduler also lets you define an end condition and customize what should be copied to each new ticket.

This can be especially useful when a recurring maintenance ticket also includes child work items or subtasks, because the whole structure can be recreated automatically instead of creating each work item separately.

Best,

Dorota

[Olga Cheban _TitanApps_]

Hi, @Mark Revely !

Setting up recurring maintenance tickets makes a lot of sense. You don't want to remember to create the same generator checks by hand every time.

Native Jira Service Management doesn't create tickets on a schedule out of the box. You'd normally set them up manually or lean on automation rules for each one.

For this, I can recommend our solution, Smart Templates for Jira. It allows you to save any Jira work items or JSM tickets as reusable templates and generate them automatically on a schedule. So, you can build a template for each maintenance ticket once, then save it as a template with Smart Templates, and schedule it to be created on a recurring basis. So all the tickets you need will appear automatically when they're due.

Here's what the Scheduler looks like:

The interface is simple and intuitive, and you don't need to configure any Jira automations. You will be able to set your preferences and view scheduled runs.

I hope this helps! Let me know if you have any questions

[James Gamble]

Hola Mark,

@Gabriela - LeanZero’s right that automation is the usual way to handle this, and since the two maintenance tickets have different schedules, I’d create a separate rule for each one.

There are actually two good ways to set it up. You can open an existing maintenance ticket and use Jira’s recurring work option to clone it on a schedule, which is useful when you want each new ticket to inherit most of the original fields. Here's a support article about it.

You can also build the rules manually under Project settings > Automation using a Scheduled trigger followed by a Create work item action. That gives you more control over the request type, summary, description, assignment, components, due date, and any maintenance-specific custom fields. For JSM, I’d make sure you explicitly set the request type in the rule so the new ticket appears correctly in the portal and uses the expected request configuration.

The exact schedule depends on what “recurring” means for each generator. For example, monthly on a particular date, every 30 days, and the first Monday of each month are three different schedules and shouldn’t be treated as interchangeable. Atlassian talks about scheduled triggers here.

Thanks,

James

[Gabriela - LeanZero]

The Set to recur shortcut James pointed at is the cleaner path, and I was too absolute yesterday saying JSM has nothing native. It does work on JSM Cloud.

Worth flagging for Mark though, since maintenance usually runs monthly or quarterly: the Set to recur quick-pick only offers daily, weekly, and fortnightly. You won't get monthly from that dropdown. What works is to open the automation rule it generates for you (System > Global automation, it's the recurring clone rule) and change the schedule there to a monthly rate or a cron. Or skip the shortcut and build a Scheduled-trigger rule with a Create action, same thing underneath.