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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,560,231
Community Members
 
Community Events
185
Community Groups

Automation of Sub-tasks

We currently have recurring tasks and have set these up as Sub-Tasks within Jira Software (server)

I am looking for the functionality that will automatically create a new Sub-Task once last months sub-task has been completed?

We currently have Automation for Jira server (within our DEV environment) but I cannot seem to get this to work for sub-task to sub-task.

It will create sub-tasks off parent issues but not at the subtask level.

Thank you for your help

1 answer

1 accepted

0 votes
Answer accepted
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 03, 2020

Hi @Kelly Peck 

It should be possible - I'm using Automation for Jira (Cloud), but the options are broadly the same. This is how I did it:

  1. Create a new rule
  2. For the Trigger, choose Issue Transitioned - and set appropriate statuses
  3. Add a Condition, choose to check for the field Issue Type equalling Sub-task
  4. For the Action, choose Clone Issue - setting it for same project / issue type. As part of cloning the issue, you can choose what fields will be set

^ The action "Create Issue" didn't work here as you can't set the parent to be the trigger issue's parent - but clone utilises the trigger issue's parent and you can still decide what field values will be set like with create.

Let us know if this works for you in Server :)

Ste

Thank you @Stephen Wright _Elabor8_ 

This solution worked in Jira Server also.

Thank you I was going wrong with the Create Sub-Task, instead of clone

Appreciate your help

Kelly

Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 03, 2020

No worries :) - if this answer works for you, would you be able to press "Accept Answer" so other users know this is the right solution?

Ste

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events