Thanks, @Stoyan Stoitsev! This is exactly what I was looking for. For those who want to setup tasks that are always done annually, you can use the Advanced CRON expression rather than Fixed rate scheduled (based on number of days). For example:
0 0 12 1 NOV ? = November 1st of any day of the week (?) at exactly 12:00:00 UTC.
Using a Fixed rate schedule of 30 days is nice, but doesn't work so well if you want to generate an issue on the first day of the month, etc. (and it's not the first day of the month when you're creating the automation). Another CROM expression that would handle it for you:
0 0 12 1 * ? = The first day of every month at 12:00:00 UTC
Or maybe you only want it to get generated on the first weekday of the month so it doesn't land on weekends (yes, the added "W" is all it takes):
0 0 12 1W * ? = The first day of every month at 12:00:00 UTC
Here's all the CRON goodies:
this solution is a joke. not necessarily by you but by atlassian. proposed solution requires the jira automation add-on. so firstly, i can't even find that add-on in the marketplace because it's a fricking mess, so i can not look up the pricing for that.
anyhow, a colleague tried some automation rules and was really impressed and liked it a lot. just to find out that there's a ridiculous limit for free use. so this means just so i could have recurring tasks (which again is an absolute basic feature), i should pay for an add-on. i mean, it's not that we are using a free product here.
@Peter Chodakowski you are correct that there are some recurring configurations that can be handled using the GUI (Basic). It even has a "Years" option to do something annually... except there is no way to tell it what month/date to start doing it. You can only start it today and it will kick off a year from today.
@Metod Kana I didn't need to add any add-on, as far as I can tell. I just go to Project -> Settings -> Automation and it's there. I am on the cloud instance, but I assume you are, too.
Hi @Metod Kana,
I've run into the same problem in JIRA Standard: << you've reached your automation limit >>. There's no limit in JIRA Advanced.
Anyway, I found that the above said limitation apply just if you set a multi-project rule. It means: you define the rule just once, and select to apply it to more than one project.
There is no limit for mono-project rules (1 rule - 1 project). So, you can copy-paste the same rule to all the Project you need. I know it is not ideal, but at least it works.
Yes it is possible to create recurring tasks in Jira. You can find a tutorial in this page:
Don't use SAL's scheduler - it's in the process of being deprecated. There's now a new scheduler at https://bitbucket.org/atlassian/atlassian-scheduler which replaces SAL's scheduler. There's an example of how to use it at https://bitbucket.org/cfuller/atlassian-scheduler-jira-example
Writing recurring tasks app from scratch might be a nightmare. There are many factors you need to consider:
In most cases, ready-to-use apps will be a better solution. Most of them are paid but you get a good product with support in return.
I use a cron script that pokes things in over the REST API, but for something a bit less reliant on a bit of command line stuff, yes, you can do it.
There are several add-ons in the marketplace that can do it with a friendlier UI from within Jira, and the generalised tools like Automation and ScriptRunner enable you create regular processes.
You can, of course, write your own too. Have a look at https://developer.atlassian.com/docs/atlassian-platform-common-components/shared-access-layer/scheduling-events-via-sal-tutorial if you want to do it yourself.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events