Key takeaways
- Jira Cloud can repeat a work item natively: open it, click the lightning bolt or the due date, and choose Set to recur.
- Behind the scenes Set to recur creates an automation flow, so every repeat counts toward your automation allowance.
- For more control (a monthly report on the first Monday, a different assignee each time), build a Jira automation rule with a scheduled trigger instead.
- Jira repeats the work but doesn't check whether people have time for it; a weekly 2-hour review quietly takes 10% of someone's week.
- ActivityTimeline shows recurring work and meetings on each person's timeline, so the plan accounts for them. You can try it free for 30 days.
Every Monday someone opens Jira and creates the same issue again: "Weekly status report", same description, same assignee, new due date. After a few months it's 50 copies made by hand, and the week someone forgets is the week the report was needed.
Here's the short answer: Jira Cloud can now repeat a work item on its own. For anything more complex than "every week", a Jira automation rule does it. Below are both, a manual fallback, and how to make sure the recurring work actually fits into your team's week.
What are recurring tasks in Jira?
Recurring tasks are issues that come back on a schedule with the same content: a weekly report, a monthly invoice run, a quarterly access review. In Jira each repeat is a separate issue, so it can have its own assignee, due date and work log.
Common recurring tasks examples include:
- Weekly Status Meetings: Regular check-ins to discuss progress and plans.
- Scrum Ceremonies: Sprint planning, review, retrospective and product backlog grooming.
- Monthly Reports: Generate and review project performance reports.
- Maintenance Tasks: Routine system and equipment checks.
- Invoice Processing: Monthly billing and invoicing.
How to create recurring tasks in Jira
1. Set to recur (Jira Cloud, quickest)
- Open the work item you want to repeat and set its due date.
- Click the lightning bolt icon (Automation) or the Due date field.
- Choose Set to recur.
- Pick the schedule, or make it repeat when the current one is done, and set when the repeating stops.
Jira clones the work item each time. The copy keeps the fields and child work items, gets a new due date from the schedule, and shows a recur icon next to the due date. Attachments, links, linked work items and Confluence pages aren't copied.
To stop it, open the work item, click the lightning bolt or the due date, and delete the recurrence under Recurring.
2. An automation rule with a scheduled trigger (Cloud and Data Center)
Use this when Set to recur's options aren't enough, for example "the first working day of the month" or a different assignee each time.
- Go to Project settings → Automation and create a new rule.
- Choose the Scheduled trigger and set the time. Advanced cron expressions cover cases like "first Monday of the month".
- Add the action Create work item: project, type, summary (add
{{now.format("MMM yyyy")}}to tell copies apart), description, assignee and due date ({{now.plusDays(5)}}). - Name the rule, save it and turn it on.
3. Clone by hand (any Jira)
Open the last issue, choose ••• → Clone, and change the due date and assignee. It works anywhere and costs nothing, but it depends on someone remembering.
Which method should you use?
For most teams, Set to recur is the answer: two clicks, and the person who owns the work sets it up. Move to an automation rule when you need a schedule it doesn't offer or several work items created at once.
On usage: each run of a recurring flow counts toward your plan's automation allowance. A weekly rule with a trigger and one action uses about 8 steps a month, which is small, but Atlassian starts billing steps over the allowance from 3 December 2026, so check Insights → Platform usage if you run many.
How do you fit recurring work into your team's capacity?
Jira creates the recurring issue. It doesn't check whether the person has time for it. A 2-hour weekly review, a 1-hour stand-up every day and a monthly half-day audit add up to about 8 hours a week for one person, and none of it shows in sprint planning.
ActivityTimeline is a Jira app that shows each person's work on a timeline, with hours per day. Recurring work shows up there in three ways: recurring issues created by Jira, recurring events you add in ActivityTimeline, and recurring meetings imported from Google Calendar or Outlook.
Block time for recurring meetings and duties
Some recurring work doesn't need to be a Jira issue at all: sprint planning, a weekly client call, on-call duty. In ActivityTimeline you add it as a booking, which reserves a set number of hours on a person's or a team's timeline.
- In the Planner, click a cell on the person's row (or the team row).
- In the Create New Item dialog choose Booking and name it, for example "Sprint planning", with the hours it takes.
- Click Recurrence, choose daily, weekly or monthly, and save.
Each occurrence takes its hours out of that day's capacity, so the workload indicator shows the day as fuller, and issues you schedule around it land where there's room.
Meetings that already live in Google Calendar or Outlook don't need to be entered twice: import the calendar and recurring meetings appear on the timeline as busy time.
To set up a custom recurring task, begin by clicking on the desired cell within ActivityTimeline. Choose "Create Issue Dialogue" and then select the custom event that matches your repeated task type. After filling in the essential details and selecting the assignee (or even assigning it to an entire team), you can set the recurrence by clicking the "Recurrence" button. Customize the frequency based on your needs, whether it’s daily, weekly, or monthly, and then confirm your settings.
In a few clicks, you’ve established a recurring task that will notify the relevant team members, ensuring everyone is aware and prepared. This proactive approach enhances team collaboration and reduces the administrative burden on project managers.
See your recurring work in your own week
Each person has a Workspace: their issues from every project, their week with bookings and time off, and the hours they've logged against the hours required. Recurring issues and bookings sit in the same view, so the weekly report isn't a surprise on Friday.
How much time does recurring work take?
Recurring work is easy to underestimate because each piece is small. To see the total, label recurring issues in Jira (for example recurring), then open Timesheets in ActivityTimeline and scope it by the Jira filter labels = recurring. You get hours per person per week, and you can export it to Excel. For bookings and other events, the events report shows how many hours each type took over any period.
When a team sees that recurring work takes a full day a week, the conversation changes from "why is the sprint late" to "which of these meetings can go".
A useful feature is the ability to generate detailed capacity and resource utilization reports. These reports provide an overview of team workloads, highlight potential bottlenecks, and ensure optimal resource allocation. Customized reports can focus on specific repetitive tasks like daily stand-ups, weekly reviews, or monthly audits, enabling you to gather specific insights and make informed decisions.
With ActivityTimeline, the goal is to enhance overall productivity by providing a clear picture of how recurring activities are managed. By leveraging these reporting capabilities, your team can maintain a smooth workflow, anticipate responsibilities, and continuously improve project outcomes.
Conclusion
Let Jira repeat the work: Set to recur for most cases, an automation rule when the schedule is unusual. Then check it fits. Recurring work rarely fails because nobody created the issue; it fails because nobody planned the hours.
If you want to see where recurring work sits in your team's week, try ActivityTimeline free for 30 days on your own Jira.
