Moving an existing Story to be a sub-task for an Epic


I have an existing story(STORY-A) in a project. This story has sub-tasks of type Technical Tasks (TECHTASK-1, TECHTASK-2, TECHTASK-3). I have an epic (EPIC-A) which currently has Technical Tasks (TECHTASK-A, TECHTASK-B). I would like to move STORY-A to be a sub-task under EPIC-A.

After I move, I would like the hierarchy to look like

  1. EPIC-A
    • STORY-A
      • TECHTASK-1
      • TECHTASK-2
      • TESCHTASK-3

I would like to know what admin settings are needed from the Issue Type or schema settings are needed on the GreenHopper side to setup something like this.

Thanks and regards,

2 answers

1 accepted

You can use epic labels in GH to group stories, tasks or whatever under an epic.
If i understand that right you want to convert a story with own sub-tasks into a subtadk itself. That wont work cause the existing subtasks won't become sub-subtasks.

Thanks, this helps. So GreenHopper can have only 2 levels at the max at any given point.

Suggest an answer

Log in or Join to answer
Community showcase
Louis De Jaeger
Posted Thursday in Off-topic

Friday fun: your best joke

Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...

189 views 12 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot