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

[Gabriela]

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.

[James Gamble]

Hola Mark,

@Gabriela’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