Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you handle recurring tasks?

Antonia
Contributor
August 8, 2025

I would do this with automation, but would you then create a separate request type for each task?
For example, “Set up Surface” or “Update server.”
These are two different things, probably with different fields.
So how would you recommend I do this?

2 answers

3 votes
Walter Buggenhout
Community Champion
August 8, 2025

Hi @Antonia,

That definitely depends. If you really need different fields (and these fields are worth tracking as separate attributes on your work items for reasons like search, reporting, ...), then you have a good argument to create separate work types (or request types in JSM) for it. The same would be true if they follow a different workflow, for example.

But if the information you want to add to these different tasks is purely informative (so people can read from the task what they should do, but there is no further need to do anything specific with the details, then having them just as separate recurring tasks of the same type, but with a different summary and description should do the trick as well.

I would recommend taking a pragmatic approach to this.

Hope this helps!

1 vote
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 8, 2025

Hi @Antonia 

I agree with @Walter Buggenhout 

I did implement this multiple time, I create a new work. type for this for customers, like "Reoccurring Task"

This as this made reporting easier and would be easier to no to be used in SLA's or to easily set specific SLA's around the work type.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events