Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automated Transition Loop For Recurring Tasks

My organization has some reporting and invoicing tasks that need to be repeated monthly. We don't like the build-up of clones that occurs when issue creation is simply automated, instead we just want the same issue to automatically transition back to TO-DO monthly (or in some cases weekly). 

So if I created a Monthly Reporting epic today for example, and I know that we need to start working on it on the 20th of every month, then that same epic would boomerang back to the TO-DO column every month on the 20th, or every week on Wednesday...something along those lines. 

Has anyone else created an automation like this? Please share how you did it. I am relatively new to the platform and eager to learn

1 answer

1 vote

Hi @Aislin Percival and welcome to the community!

For tracking and reporting, it's usually best to just have new issues each month.  Are you tracking this in a Kanban project?  If so, you may just need to adjust the configuration to drop resolved issues from the board after x amount of time.

If you're still of the mindset that you want to keep reusing the same issues, you could do something with automation:

  • TRIGGER: Scheduled (Set up on 1st of every month or whatever works best for you)
    • "Epic Link" = YourEpicKey
  • ACTION: Transition Issue to To Do

Note - This assumes your project is company managed.  If you're working with a Team Managed project, you'll want to use replace "Epic Link" with Parent

@Mark Segall Thank you so much!

So, we are on a team managed board currently while we work within on admin organization--to test your suggestion above this morning, I used "Parent"=TheEpicKey and it transitioned all of the child issues to TO-DO but not the epic itself. This was on an experimentation board I created where I had the Monthly reporting set up as an epic with children 

In a team managed board, does the issue we want on a loop basically just need to be a story/task/"not an epic"?

Again, thank you so much for your assistance. I am starting to understand things more.

Mark Segall Community Leader Jan 05, 2023

If you want to include the Epic, you can change the JQL to this:

Parent = YourEpicKey OR Key = YourEpicKey
Like Aislin Percival likes this

@Mark Segall Worked like a charm!

Have a great day :)

Like Mark Segall likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events