Why use Structure plugin?
Structure plugin makes Atlassian JIRA a perfect tool for planning, mind mapping or task decomposition. Project managers can make extensive plans and monitor progress using JIRA issues. Project team members can break down tasks into smaller pieces for more precise estimation and reporting.
See also: Why Structure?
How is issue hierarchy provided by Structure plug-in different from the standard sub-tasks?
Sub-tasks have several major limitations:
- sub-tasks are only a one-level hierarchy;
- sub-tasks are separate issue types;
- sub-tasks always inherit project and security level from their parent task.
None of these limitations are present in Structure. At the same time, Structure plugin provides all the features that sub-tasks have, and more.
See also: Basic Concepts
What about Greenhopper?
You can use Greenhopper and Structure side by side. Structure plugin stores its data in a separate place, so it will not conflict with any other plug-in.
By default, Structure's hierarchy and issue order are independent from GreenHopper, but you can install a GreenHopper Synchronizer to have GreenHopper Rank synchronized with the position in the Structure and GreenHopper Epic/Theme field synchronized with the stories being under epics in the Structure.
Should I disable sub-tasks to use Structure?
Not necessarily. While Structure plugin can be a good replacement for sub-tasks, they can be used in parallel — for example, if you want to try Structure on a single project without affecting other JIRA users.