- 
    
Suggestion
 - 
    Resolution: Unresolved
 - 
    None
 
- 
        7
 - 
        30
 - 
        
 
In Version One, we could create a hierarchy of Epics, but we don't seem to have this capability in Greenhopper. Is this something that can be provided?
- is blocked by
 - 
                    
JRASERVER-4446 Sub-issues should be able to contain their own sub-issues
- Closed
 
 
- is duplicated by
 - 
                    
JSWSERVER-5356 Story Hierarchy support in Greenhopper
- Closed
 
 - 
                    
JSWSERVER-8044 As an admin, I would like to be able to configure a hierarchy navigator with an issue type(s) so that it would know how to build a tree, on a given issue
- Closed
 
 - 
                    
JSWSERVER-8755 Integrate Structure and Sprint Planning
- Closed
 
 - 
                    
JSWSERVER-9045 Support for Groups of Epics or Themes
- Closed
 
 - 
                    
JSWSERVER-9077 Add the ability to separate subtasks from parents
- Closed
 
 - 
                    
JSWSERVER-9444 It would be great to be able to easily create heirarchies of Issues, Components and Versions
- Closed
 
 - 
                    
JSWSERVER-9809 Ability to link issues to stories and not just epics
- Closed
 
 - 
                    
JSWSERVER-7203 Add the ability to create multiple Epic issue type in JIRA Software
- Not Being Considered
 
 
- is related to
 - 
                    
JSWSERVER-2420 As a GH user, I want to work with a tree view of my epics within the planning board
- Closed
 
 - 
                    
JSWSERVER-11665 Assign Sprints to Subtasks and Parent Reflects Current Subtask Sprint Estimation
- Closed
 
 
- relates to
 - 
                    
JSWSERVER-21393 The session "Issues in Epic" should be based on Hierarchy
- Gathering Interest
 
 
- mentioned in
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...