Skip to main content
replaced http://pm.stackexchange.com/ with https://pm.stackexchange.com/
Source Link

In this answeranswer, an epic-story structure is suggested. I like this approach and I'm trying to utilize it. But, the problems how to handle priorities. More specifically, assume I have two epics (e1 and e2) and each has three stories (s11, s12 and s21, s22). My goal is to prioritize the epics (say that e2 is more urgent than e1) and inside each epic prioritize the stories. Eventually, I want the backlog to show the prioritization based one epic/story.

Example:

  1. Epic 2
  2. Story 22
  3. Story 21
  4. Epic 1
  5. Story 11
  6. Story 12

Currently, it seems like stories and epics are completely mixed in the backlog and there's no way to fine tune the priorities.

In this answer, an epic-story structure is suggested. I like this approach and I'm trying to utilize it. But, the problems how to handle priorities. More specifically, assume I have two epics (e1 and e2) and each has three stories (s11, s12 and s21, s22). My goal is to prioritize the epics (say that e2 is more urgent than e1) and inside each epic prioritize the stories. Eventually, I want the backlog to show the prioritization based one epic/story.

Example:

  1. Epic 2
  2. Story 22
  3. Story 21
  4. Epic 1
  5. Story 11
  6. Story 12

Currently, it seems like stories and epics are completely mixed in the backlog and there's no way to fine tune the priorities.

In this answer, an epic-story structure is suggested. I like this approach and I'm trying to utilize it. But, the problems how to handle priorities. More specifically, assume I have two epics (e1 and e2) and each has three stories (s11, s12 and s21, s22). My goal is to prioritize the epics (say that e2 is more urgent than e1) and inside each epic prioritize the stories. Eventually, I want the backlog to show the prioritization based one epic/story.

Example:

  1. Epic 2
  2. Story 22
  3. Story 21
  4. Epic 1
  5. Story 11
  6. Story 12

Currently, it seems like stories and epics are completely mixed in the backlog and there's no way to fine tune the priorities.

Bumped by Community user
Source Link

Epics and stories prioritization in JIRA

In this answer, an epic-story structure is suggested. I like this approach and I'm trying to utilize it. But, the problems how to handle priorities. More specifically, assume I have two epics (e1 and e2) and each has three stories (s11, s12 and s21, s22). My goal is to prioritize the epics (say that e2 is more urgent than e1) and inside each epic prioritize the stories. Eventually, I want the backlog to show the prioritization based one epic/story.

Example:

  1. Epic 2
  2. Story 22
  3. Story 21
  4. Epic 1
  5. Story 11
  6. Story 12

Currently, it seems like stories and epics are completely mixed in the backlog and there's no way to fine tune the priorities.