You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In a nutshell, I'm looking to create a template so team members can use a standardize structure to manage our software projects. That way we ensure all tasks are completed throughout the project phases without oopsie daisies.
Basically the structures starts with a new issue type called initiatives which is set above epics, stories and then tasks. I intend to use initiatives as projects, where epics are the project phases the team goes through when working the project. Lastly, stories are the tasks for each phase. Please refer below for a visual representation of the structure.
While the Configuring initiatives and other hierarchy levels documentation, states that initiatives level is only available for premium plans, I'm trying to include epics as related issues to initiatives in order to classify and follow the structure aforementioned.
I was able to create an automation that clones the initiative issue but can't for the life of me make it to clone the related epics along with its stories within. Please find screenshots below with the automation configuration:
What am I doing wrong in the automation rule?
Environment: Jira Cloud
Project: Company Managed
Issue Type Scheme: Custom with levels Initiative > Epic > Story > Tasks > Sub-tasks
Hi @Antonio Rivera,
I am Marlene from codefortynine.
If you are open to try a Marketplace app, you can try Deep Clone for Jira.
With our app it is possible to clone entire issue trees and keep their hierarchy.
If you have questions about our app, let us know.