Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

Hierarchy in Jira

Hey Community!  I am new to JIRA and have been deeply involved in the planning and structure of TFS hierarchies. The paradigm shift to JIRA with my historical EPIC, FEATURE, US, TASK of TFS has thrown me off. Can anyone guide me in how they are utilizing Epics?  I am currently reorganizing backlog structure and would love to hear how others are leveraging their environments. 

I have shifted to JIRA Epics being “features” to encompass the overall body of work and decomposing the user stories leveraging sub-tasks for internal team and tasks for external team. My thoughts are that the subtasks are prerequisites for the closure of stories. The subtasks represent dependencies and items to meet acceptance criteria for validation of completion of the stories. The tasks, on the other hand, are for tracking external team work and validation.  Easier for team to track, for demoing team diligence and ownership. 

Would love to hear your thoughts and guidance. 

Thanks!

2 comments

Here is a snapshot from our documentation. The Initiative layer becomes available with Jira Portfolio I think.

Screen Shot 2020-01-13 at 2.31.08 PM.png

Like Zach Noyce likes this
Kevin Bui Atlassian Team Jan 12, 2020

Hi @Zach Noyce

I have shifted to JIRA Epics being “features” to encompass the overall body of work and decomposing the user stories leveraging sub-tasks for internal team and tasks for external team. My thoughts are that the subtasks are prerequisites for the closure of stories.

I think this is a viable way of looking at it. I usually think of Epics as being large bodies of work that span multiple sprints, which then break down into mid-level issues (stories, bugs, tasks). I don't use subtasks in my Jira projects, but I've seen other teams get value out of subtasks as a way of tracking each aspect of a Story/Bug/Task. ie: If a task is particularly complex and requires 2 or 3 people to work on different aspects of it.

Atlassian provides some guides on Epics that you might find useful:

Like Zach Noyce likes this

Comment

Log in or Sign up to comment
TAGS

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you