nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Vinay Hosamane1

Hello,

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

EPIC-A
- STORY-A
  - TECHTASK-1
  - TECHTASK-2
  - TESCHTASK-3
- TECHTASK-A
- TECHTASK-B

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,
Vinay

Accepted answers

C.Faysal {CFcon}

You can use epic labels in GH to group stories, tasks or whatever under an epic.

All comments

C.Faysal {CFcon}

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.

C.Faysal {CFcon}

You can use epic labels in GH to group stories, tasks or whatever under an epic.

Vinay Hosamane1

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud