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

Automation to move Stories to Epics

Hi JIRA community!  

I would like your advice on how I can optimize my JIRA adminstrative work via automation.  We have about 8 timebound epics that close every month and any of the remaining stories that are not completed are moved into another epic that is created at that time. 

The way I do this today, is the following: 

1) I use the bulk upload functionality to create the 8 epics

2) For each Epic, I use a custom JQL search to pull back any stories that are not closed within that Epic and bulk update them to use the new epic ID as the parent. 

3)  I close the old Epic by dragging it across the board.

4) I move the new Epic into IN PROGRESS (requires about 4 transitions to get from backlog to In Progress).

5) I repeat these steps for the remaining epics.

Is there a way to speed this up even more through either some script or automation plugin?  Thanks! 

1 answer

1 accepted

1 vote
Answer accepted

Hi @Ryan Lagola 

Yes, that is possible with the Automation for Jira addon.  There is a free (Lite) and a paid (Pro) version for Server/Data Center Jira, so check with your site admin if you have either of these.

I recommend creating a test rule in a test project first, for one of the epics, using a manual or scheduled trigger.  And then evaluate what is common/different for the epics.  That will help you decide if you can collapse these down and do them with one rule, branching over the epics...or with separate rules.

If you have challenges creating the rules, please post images of your rule and the audit log details and the community can help you.

Kind regards,

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events