🗓️ Save time by scheduling work in Jira

[Hercules Konstantopoulos]

@Eoin just jumping on this cadence comment: it would be rad if we could get the same calendar functionality as we have in Automation with the 'Scheduled' trigger: 

[Robin Powell]

@EoinWe don't really use due dates, so the value for us would just be in the creation of the issue.

[Lianne Geerlings]

@Eoin  My work items are mostly related to monthly or annual checks.  For me creating the work item every month will give me value.

[danielwould]

I thought I might chime in here, since I'm happy to see the start of an 'official' support path for recurring tasks, having built out automations for this myself, I'm always keen to drop custom implementation. However as noted it seems this version is still a little primative.
I handled this by introducing labels for WeeklyTemplate, MonthlyTemplate, QuarterlyTemplate and an association automation rule that runs weekly/monthly/quarterly that looks for issues with that template and clones them, removed the label from the old after it has a new 'latest'. It also creates a 'cloned link' relationship between the old and new.
this relies onf also having an automaiton on issue create that can tell this is a cloned eg story - so that it can query the clone source to find the subtasks then also clone those. which is a bit of a faff but works arond the otherwise inability to clone a task and it's subtasks.
The advantage here is that I have 1 rule per reoccurrence rate not lots of different ones.
to solve the isue @Eoin mentioned about targeting the right day - I introduced a single new field 'T-Plus' so that an issue states how many days past it's reference point (start of week/start of month etc) it is supposed to be due. I can then use the built in business days feature to figure out which date is that many business days into the target period.

I go another step further to auto create reocurring epics that 'own' all the recorrding tasks in a given month so that when I spawn new issues I look for the epic that start/due spans the target reoccurance date and link them. So the team can easily manage each batch of reoccuring tasks.

Whilst this was a little complicated to setup initially, it has been running very well for several months. I'd love to see a native jira implementation with a lot of the same capabilities that allows me to decommission custom logic.

[Eoin]

Thanks @Hercules Konstantopoulos We're providing a super simple overlay on existing automations functionality in a contextual location to validate if this is more approachable way for people to avail of the power that exists within Jira. The risk is we make it too complicated by adding too many inputs. We'll monitor for feedback and see if this is something we will expand on. Cheers

[Eoin]

Thanks @danielwould for sharing!!! :) Very impressive and thanks for the suggestion.

[Sherritt_ Leticia]

@Eoin , we have activities that need to be done monthly, quarterly, once a year or twice a year. It would save so much time and human error if the recurrence could be set to a monthly cadence every X number of months or days rather than seeing so many options on the menu, For these type of recurring activities we have a few days of tolerance, so if a ticket is opened on the 31st and set it to reoccur every X months on schedule, we would expect the next ticket would be opened at the end of the month whether it is the 28, 30th or 31st but if it is set to reoccur every 30 days on schedule then it would be opened exactly every 30 days.

I hope that makes sense and I hope even more that this feature can get to this point soon!

Thanks!

[Yatish Madhav]

@Eoin how can one see additional enhancements, improvements or fixes to this recur feature specifically

We have an app that we are paying for that we potentially can save costs on and want to vet and do a apples-to-apples comparison so that we can effectively switch over to this? Thanks, Yatish.

[Amy Schindel]

I just came out of a meeting where I was helping to onboard a new department to Jira.  They loved the idea of this feature, but like many others need an option for monthly, quarterly or yearly.  I think an option for every XX weeks would be great, and then every XX months would probably be "good enough" for most people?  This kind of logic is already built into many calendaring systems (I've used both Google and Outlook calendars to set something to reoccur every 4 weeks or 4 months).

[Eoin]

Hi @Yatish Madhav We're hoping to include a monthly option but no other improvements have been confirmed yet. The expectation is that we will keep this contextual setup point very basic. The automations experience is where you can have more flexibility when setting up recurring work. 

I hope this helps.

Thanks

[Eoin]

Thanks @Sherritt_ Leticia @Amy Schindel for the feedback. In the meantime, we highly recommend having a project admin set up less frequent recurring work or work that has more complex recurring schedules. We'll continue to gather feedback to see whether we expand on the flexibility in the due date entry point so your feedback is very valuable. 

Thanks

[Yatish Madhav]

OK Thanks @Eoin -

Yeah, please include an annual and monthly option. This is so that we do not need out lesser technical users to have to dig into automation as I am almost certain most users will simply as admins for this instead of further customizing it in the automation rule.

2 other things that will make this more powerful is, removing the expiry and allowing cron like schedules too

Thanks, Yatish

[Jaap Scheper]

I want to create a recurring task to not forget to update Client Secrets, that expire every 24 months.

We need the configuration "Repeat every [X] [days/weeks/months] starting at [startDate], ending [endDate]"

I have now used the normal automation rules to accomplish this task.