🗓️ Save time by scheduling work in Jira

[#1]

We’re making big changes to make Jira the best work management tool for every knowledge worker on every team. One recent change is making recurring work effortless by allowing you to schedule work.

So whether it's a daily social media post, a weekly status update, or a fortnightly sprint retro - we’ve got you covered!

Our aim is to reduce the effort required to recreate work multiple times, improve consistency and quality, and ensure work isn’t overlooked. We want you to focus on driving successful outcomes rather than on the more tedious work.

Set a work item to recur automatically

1. Open the work item you want to recur automatically.

2. Select Actions (coming soon: click on the Due date field)

3. Locate the menu item Set to recur.

4. Fill in the recurring details— when the work item will recur, the trigger, and when the rule will expire. The trigger can be a schedule, and additionally incorporate whether the work item has been completed.

What happens when the work item recurs?

When the work item recurs, it inherits the automation rule which will be turned on automatically. All fields and child work items will be copied to the newly created work item; except for Attachments, Start date, Due date, and Links

The due date of the recurring work item will be automatically set based on the scheduled frequency. For example, in a weekly schedule, the due date will be set to seven days after the creation date of the work item.

A “recur” icon will appear next to the Due date field in the work item view and next to the work item summary in the Calendar view.

Admin controls

Project admins can disable the rules from within the automations rules view.

1. From within your project, select Project settings > Automation.

2. Select the Rules tab to view a list of all your created automation rules.

3. You can filter the list of rules using the Rule name and the Labels. The Rule name is “Clone on a schedule” and the Label is “Recurring.

4. Depending on your permissions, you will be able to Delete and/or Disable the rule.

Global admins can disable the ability for non-admins to create and manage recurring work rules.

1. Select> System.

2. Select Global automation.

3. Select > Global configuration.

4. Uncheck Allow non-admins to create recurring rules

Frequently asked questions

Questions	Answers
Why don’t I see these changes on my site?	Your site may be enrolled in Release Tracks, where changes are bundled and shipped together at one point during the month. Don’t worry, it just might mean you have to wait a few extra weeks.
Can any users schedule a work item to recur?	Yes, any user can do this. However, Global admins can turn this off at the site level.
Does this contribute to my automation usage limits?	Yes, because this is built on Jira automation, each work item created on a schedule will count towards a rule execution. Learn more about automation usage limits here.

Please share how you are using scheduled work in the comments below!

Regards,
The Jira team

[Lianne Geerlings]

I am really happy seeing this functionality!

In my case it would add value to see a Recur period for Yearly periods. An option that you could extend the due date for just another year (quarter or month and change the status at the same time.

[Jimmy Seddon]

@Eoin I can appreciate what you are trying to accomplish, but this is a very poor implementation.  The moment I read this article, I have gone and turned off this setting . 

We have over 2000 users in Jira, and several automation rules that are critical to our business functioning.

This "feature" feels like a very easy way for our users to unknowingly burn through our Automation usage limits and that would have extremely significant impacts to the larger instance.

Thank you for giving me the control to turn this off, if that wasn't provided we would be having a very different conversation.

[Matt Doar _Adaptavist_]

Neat idea, but allowing users to schedule repeating work shouldn't put the rest of the Jira instance at risk. As Jimmy said, I'd recommend non-Premium customers disable this for now

[Rick Westbrock]

We are on the Continuous release track but I don't see the new global setting which was surprising because the impression I got from the first row of the FAQ table above was that the only reason we wouldn't see it is if we were on the Bundled release track.

[Dirk Lachowski]

@Jimmy Seddon @Matt Doar _Adaptavist_ @Eoin That’s maybe the wrong discussion. The real question is: Why do recurring tasks burn automation credits? Imagine Asana (or Todoist, or Monday,  or whatever) is adding a “recurring tasks fee”. Wouldn’t be smart, right?

Hey Atlassian, I understand that bills need to be paid, but come on, recurring tasks with a price per recurrence? That’s a new level of low. And why would anybody adopt this feature? If i have to pay for it, i can just keep using one of the marketplace add-ons that don’t burn through credits. Or keep my recurring tasks whre they’re right now - in Todoist. Running out of credits is a price that’s too high for convenience. And it’s a broken feature. What if we run out of credits and the next task not recurring because of that is “pay Atlassian bill”? So, what we got is: “Tasks scheduled as recurring MAY recurr, but you won’t know and we won’t tell you. And by the way, we’ve just stopped ALL automations for the next 13 days, but you can add 50 users to fix that - nah, make it 100, just to be sure. And did I mention that you need to be on Premium?”.

So, this is a nice feature, but automations running because of it must not reduce the automation credit count. The thing is, automations are for your customers, we pay for them to automate our stuff. If you need automations for your stuff, I do not see why that’s on my budget - it’s on yours. If you can’t do that, then don’t add that feature. Currently you’re a landlord who’s running his fridge on my energy bill - don’t be that guy.