How to Set Up Jira Recurring Tasks: A Step-by-Step Guide
Tired of recreating tasks by hand? Set up Jira recurring tasks with automation, test them safely, and keep work on track. Read now to learn how.
Recurring Jira tasks can quietly disappear from a team’s routine. A weekly review gets missed, a monthly access check slips, and someone ends up creating the same issue by hand again.
That manual work adds up. It also makes ownership, due dates, and completion history harder to keep consistent. A task that repeats every Monday should not depend on someone remembering to recreate it.
But here's the truth: Jira can create recurring tasks automatically with an automation rule. In this guide, I’ll walk you through setting a schedule, creating the right issue, testing it safely, and keeping the rule useful as your workflow changes.
How to Set Up Jira Recurring Tasks
The simplest approach is a scheduled Jira automation rule that creates a new issue at a chosen interval. You can use it for weekly reviews, monthly maintenance, or other repeatable work.
- Choose a recurring task. Write down its project, issue type, summary, owner, priority, and schedule. For example, a team might need a “Review open support tickets” task every Monday.
- Open project automation. In Jira Cloud, open the project, choose Project settings, then select Automation. Your access and Jira configuration may affect which automation settings you can see.
- Create a rule with a scheduled trigger. Select the option to create a new rule, then choose Scheduled as the trigger. Set a frequency, such as every Monday at 9 a.m., and confirm the time zone.
- Add an issue-creation action. Choose Create issue, then select the project and issue type. Add a clear summary, description, priority, and other fields your team needs.
- Set ownership and timing. Add an assignee if the same person owns each occurrence. If your process allows tasks to be assigned later, leave the field empty and explain the handoff in the description.
- Name and enable the rule. Use a descriptive name, such as “Create weekly support review task.” Review the rule details, turn it on, and check its audit log after the first scheduled run.
Here's why: a scheduled trigger controls when Jira runs the rule, while the create-issue action defines what each new task contains. Keeping those roles clear makes later edits easier.

Decide What Should Repeat
Before setting a schedule, distinguish a recurring task from a task that should reopen. A new issue for each occurrence gives you a separate record of every week’s review or month’s inspection.
Reopening one issue can make sense when the work is a single ongoing responsibility. However, it can blur completion history. For example, a monthly review recorded on one issue may not show which month’s checks were completed.
Choose a frequency that matches the work rather than someone’s habit. A weekly review may need a new issue every Monday, while a quarterly access review may only need a reminder every three months.
Configure the Schedule and Issue Fields
A useful recurring task carries enough context for someone to act without asking what it means. Use a specific summary, such as “Review overdue support tickets,” instead of “Weekly task.”
In the description, state the expected action and completion criteria. For a weekly ticket review, you might ask the assignee to check tickets older than seven days, add a status comment, and flag blockers.
For tasks that need a due date, set a date relative to the run time if your Jira rule configuration supports the relevant smart values. Test the date format and time zone; a value that works in one field may not work in another.
Prevent Duplicate or Poorly Timed Tasks
A scheduled rule that creates a fresh issue each time is simple, but it can produce duplicates if someone creates another rule for the same task. Give each rule a clear name and check existing automation before adding a new one.
Consider the time zone and working calendar. A 9 a.m. schedule may run at an unexpected local time after a team member changes settings or when daylight saving time shifts.
If a task should only be created when a condition is met, build and test that condition carefully. For example, a maintenance task might only be appropriate for an active project. A broad condition can create clutter across unrelated work.
Test and Maintain the Automation
Review the rule before enabling it. Confirm the project, issue type, summary, assignee, schedule, and any required custom fields. If Jira blocks the rule, check permissions and required field settings.
After the first run, inspect the created issue and the rule’s audit log. Confirm that the task appeared once, at the expected time, with the correct details. If the run failed, the log can point you toward a missing field or permission issue.
Set a reminder to revisit recurring rules when ownership, project structure, or team routines change. A monthly task assigned to someone who has left the project will keep generating work that no one can easily complete.
Recurring Task Management with ONES.com

Value Proposition
ONES.com brings project management and knowledge management together on one platform, with AI assistance through ONES Assistant. ONES Project is its project management product and can serve as a Jira alternative for teams that need recurring work, custom workflows, and deployment flexibility.
Core Capabilities
- Manual repetition creates missed work → ONES Project supports automation and custom workflows → teams can reduce repetitive task creation and define how recurring work moves through the process.
- Different tasks need different fields → Custom fields let teams capture details such as review period, system owner, or maintenance category → each issue can carry the context its assignee needs.
- Teams lose visibility across repeat cycles → Built-in reporting helps teams review project progress → leads can spot unfinished work and recurring bottlenecks.
- Agile teams need planned cycles → Sprint management supports work organized into sprints → teams can coordinate planned tasks alongside operational responsibilities.
- Familiar Jira processes matter → Jira-compatible workflows help teams retain familiar process patterns → moving to a Jira alternative can require less workflow rework.
- Too many add-ons can complicate maintenance → Core project capabilities are available within ONES Project → teams may be able to reduce reliance on plugins for common project workflows.
- Restricted environments limit deployment choices → ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments → organizations can choose an environment that fits their requirements.
- Self-hosting can create feature concerns → ONES.com provides feature parity between cloud and self-hosted versions → teams can select a deployment approach without giving up core functionality.
ONES.com offers a free plan for up to 30 seats. ONES Project and ONES Wiki are sold separately, so a team can choose project management or knowledge management according to its needs.
Application Scenarios
Project operations: A team can configure recurring review work alongside sprint tasks, using custom fields to identify the service or process being checked. Built-in reporting can help the lead see where reviews remain incomplete.
Restricted environments: An organization with strict network requirements can consider an On-Premise, Private Cloud, or Air-gapped deployment. This gives project teams options for managing recurring work within their operating environment.
Common Challenges and Fixes
The Rule Does Not Run
Problem: The schedule arrives, but no issue appears. The rule may be disabled, lack permission, or fail because a required field is missing.
Solution: Check the automation audit log and rule status. Confirm that the rule actor can create issues in the project and that every mandatory field has a valid value.
Tasks Appear at the Wrong Time
Problem: A task appears hours earlier or later than expected. The schedule may use a different time zone from the team’s working hours.
Solution: Review the rule’s schedule and Jira time zone settings. Run a small test before relying on the schedule for a time-sensitive review.
The Team Gets Duplicate Issues
Problem: Two similar recurring tasks appear for the same work. More than one rule may be active, or a second process may create the issue too.
Solution: Search the project’s automation rules for overlapping schedules. Keep one rule responsible for each recurring task and use distinct names to make ownership clear.
Assignees Cannot Tell What to Do
Problem: The recurring issue arrives with a vague summary and no completion criteria. Each assignee has to ask what the task involves.
Solution: Write the expected action and definition of done in the description. For example, specify which tickets to review and what status update to leave.
FAQs
Can Jira create recurring tasks automatically?
Yes. Jira automation can use a scheduled trigger to run at a chosen interval, then create an issue with the fields you configure. Availability and settings can depend on your Jira plan, permissions, and project setup. After enabling a rule, check its audit log and confirm the created issue contains the expected details.
Should I create a new issue each time or reopen the same one?
Create a new issue when you need a clear record for each occurrence, such as separate weekly reviews or monthly inspections. Reopening one issue may suit ongoing work that does not need separate completion history. Think about reporting and accountability before choosing, because the issue structure affects how easily your team can review past cycles.
Can a recurring Jira task have a due date?
It can, if the rule and project configuration let you set the due date field. You may use a date based on the scheduled run, but confirm the accepted format and time zone in your Jira setup. Test with a sample issue first, especially when the due date must fall a fixed number of days after creation.
Why did my Jira automation create duplicate recurring tasks?
Duplicates can happen when multiple rules create the same issue, when a schedule overlaps with another process, or when the rule is configured to create an issue for every matching item. Review active automation rules and their audit logs. Give each recurring task one clearly named rule, and test the rule’s conditions before relying on it.
Conclusion
Jira recurring tasks are easiest to manage with a scheduled automation rule that creates a clearly described issue at the right interval. Choose whether each occurrence needs its own issue, configure the schedule and fields, then verify the first run in the audit log.
Manual task creation can lead to missed reviews and uneven records. A carefully tested rule gives your team a dependable routine, while periodic checks help prevent stale ownership and duplicate work. Start with one recurring task, confirm it behaves as expected, and expand the process when your team is ready.