Jira Structures: A Guide to Organizing Complex Projects
Can't connect tasks, dependencies, and teams in Jira? Jira Structures helps organize complex projects into a clearer hierarchy. Click to discover how.
Complex Jira projects become difficult to manage when teams cannot see how work connects. Epics, tasks, dependencies, and cross-team plans can spread across boards, leaving people unsure what matters or where delays begin.
As the hierarchy grows, simple lists stop answering practical questions. A project lead may need to compare milestones across teams, while a developer needs a clear path from a task to its parent initiative. But here's the truth: Jira’s standard issue hierarchy may not show every relationship your team needs.
Jira Structures can help you build a flexible, visual view of related work. This guide explains what a structure is, how to organize one, and how to keep it useful as projects change.
What Jira Structures Are and How They Work
A Jira structure is a customizable, hierarchical view of Jira issues that helps you group and organize work beyond a standard issue list. Teams can arrange issues into levels, add calculated columns, and use rules to populate or update parts of the hierarchy.
Structure for Jira, now associated with Tempo, is an app that adds these views to Jira. It can display issues from multiple projects in a single structure, making it easier to review initiatives, epics, tasks, and other work together.

Structure is a view, not a new Jira issue type
A structure organizes existing Jira issues into a tree. An issue can appear in a structure because someone added it, because a rule included it, or because it relates to another issue. The structure’s arrangement does not automatically change Jira’s built-in issue hierarchy.
For example, a team might place a strategic initiative at the top, group several epics beneath it, and show tasks under each epic. Jira may treat those relationships differently in its native hierarchy, so it helps to distinguish the structure’s visual organization from the underlying issue relationships.
Common features teams use
- Manual organization: Add issues and arrange them into groups that reflect how your team plans work.
- Generators: Use rules to include issues or expand relationships, helping a structure stay current as Jira changes.
- Columns and formulas: Display useful issue fields or calculated rollups, such as progress or effort totals.
- Multiple project views: Bring related issues from several Jira projects into a shared planning view.
Here’s why the distinction matters: a structure can make a plan easier to read, but it does not replace sound issue design, ownership, or workflow practices.
How to Build a Useful Jira Structure
Start with a specific planning question. A structure designed to answer “Which epics support this quarterly goal?” will look different from one used to coordinate dependencies across delivery teams.
- Choose the purpose. Decide who will use the structure and what decision it should support. Keep the first version focused, such as tracking a product launch across three teams.
- Set the top level. Add the initiative, program, release, or other organizing item that gives the view context. If no Jira issue represents that concept, use a clear grouping approach that your team understands.
- Add the work hierarchy. Place epics, tasks, and related issues beneath the appropriate parent or group. Confirm that people can follow the connections without needing a separate explanation.
- Choose how issues enter the structure. Add key issues manually when the plan is small. For larger plans, use generators or rules that identify work through project, issue type, label, or relationship criteria.
- Show only useful fields. Add columns for owners, status, dates, or estimates when they help people make decisions. Remove fields that add clutter without changing what the team does.
- Review the result with real users. Ask a project lead and a delivery team member to find a milestone, identify a blocked task, and explain what needs attention.
Let me explain: a launch structure with 200 rows may technically contain everything, yet still hide the few issues that need action. Group by meaningful work areas and keep the first view readable.
Choose a Hierarchy That Matches the Work
There is no single hierarchy that fits every project. A product team may organize work as product goal, epic, and task. A service team might use customer outcome, workstream, and action item.
For example, imagine a website redesign with research, content, design, and engineering work. Grouping by workstream helps team leads review progress, while grouping by milestone helps executives see whether launch dates remain realistic.
You might be wondering: should you mirror Jira’s issue types exactly? Use native parent-child relationships when they represent the work accurately. Add additional visual groupings only when they answer a real planning need.
Use Rules and Fields Without Losing Clarity
Rules can reduce manual upkeep, especially when issues are created or updated frequently. A generator might bring in all open tasks from a project or expand issues linked to a selected epic.
However, a rule can also pull in unrelated work if its criteria are too broad. Test it with a small set of issues first. Check whether closed work, duplicate relationships, or unexpected issue types appear.
Columns deserve the same restraint. A plan may need status, owner, and target date, while a delivery review may need estimates and completion. The best part? You can create different views for different audiences instead of forcing every detail into one layout.
Keep Structures Reliable as Projects Change
A structure needs an owner and a review routine. When teams rename projects, change labels, or adjust workflows, the rules that populate a view may stop matching the intended work.
For example, if a generator includes issues labeled launch-2025, decide who updates that rule when the next launch begins. A monthly check can catch stale filters, missing issues, and outdated milestones before a planning review.
Also agree on what each group means. If one team uses “phase” for delivery stage and another uses it for approval status, the same label may create confusion. A short naming convention can prevent that mismatch.
Where Jira Structures Help Most
Structures are especially useful when work crosses project boundaries or requires a hierarchy more flexible than a board view. A program manager can review several product teams in one place, while each team continues working in its own Jira project.
They can also support portfolio planning, release coordination, and dependency reviews. A release coordinator, for instance, can group epics by launch milestone and display owners and statuses side by side.
But a structure is not automatically the right answer for every coordination problem. If your team only needs a short task list, a Jira board may be simpler. Use a structure when the relationships, rollups, or cross-project view add practical value.

Value Proposition
ONES.com brings project management and knowledge management together in a unified platform powered by ONES Assistant. ONES Project is a project management platform and Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative, and the two products are sold separately.
Core Capabilities
- Complex work is hard to coordinate → Jira-compatible workflows → Teams can retain familiar workflow patterns while organizing project work in ONES Project.
- Standard workflows do not fit every team → Custom workflows and fields → Teams can model their own stages and capture the information their work requires.
- Sprint planning needs a dedicated process → Sprint management → Agile teams can plan and track work through sprint cycles.
- Progress is difficult to review → Built-in reporting → Project teams can inspect progress without relying on a collection of separate reporting plugins.
- Repeated actions take too much effort → Automation → Teams can automate suitable workflow tasks and reduce routine manual steps.
- Project guidance is scattered → ONES Wiki → Teams can maintain connected knowledge management alongside project work when they choose both products.
- Deployment requirements vary → Four deployment options → Organizations can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment.
- Self-hosting raises feature concerns → Full feature parity → ONES.com offers feature parity between its cloud and self-hosted versions.
- Teams need room to evaluate → Free plan for 30 seats → A team can try the platform with up to 30 seats before deciding how it fits its needs.
ONES.com emphasizes native capabilities that can reduce reliance on plugins. Its deployment options include on-premise environments, which may matter to organizations with specific infrastructure requirements.
Application Scenarios
Cross-team product delivery: A product organization can use ONES Project to manage work across teams, configure workflows for different stages, and review progress through built-in reporting.
Restricted-network planning: An organization that needs an air-gapped deployment can evaluate ONES.com’s deployment options while planning how project management should operate in that environment.
Common Challenges and Practical Fixes
Too many issues make the hierarchy hard to scan
Problem: A structure includes every issue across several projects, so key milestones disappear among routine work.
Solution: Narrow the generator criteria, group issues by workstream, and use a summary view for decision-makers. Keep detailed execution views available to the teams who need them.
Rules pull in the wrong work
Problem: A broad filter includes issues that share a label or project but do not belong in the plan.
Solution: Test rules against a small sample and review the results with the structure owner. Add a more specific condition, such as issue type or parent relationship, when needed.
People disagree about what groups mean
Problem: One person treats a group as a delivery phase, while another treats it as a team boundary.
Solution: Add a brief description to the structure and use consistent labels. If different audiences need different interpretations, create separate views with clear names.
The view becomes outdated
Problem: Project changes leave stale rules, old milestones, or missing issues in the structure.
Solution: Assign an owner and review the structure on a set cadence. Include a quick check of generator criteria, key dates, and project changes.
FAQs
Is Jira Structure the same as Jira’s built-in issue hierarchy?
No. Structure for Jira provides a customizable view that organizes Jira issues into a hierarchy. Its visual arrangement can include groupings beyond native parent-child relationships, but those groupings do not automatically change Jira’s underlying issue hierarchy.
Can a Jira structure include issues from multiple projects?
Yes. A structure can bring related issues from more than one Jira project into a shared view. This can help with program planning or cross-team coordination. Use clear criteria and groupings so the combined view remains understandable to people who do not work in every project.
Should I organize work manually or use generators?
Manual organization can work well for a small, stable plan where someone reviews changes regularly. Generators can help when issue volume is high or work changes often. Many teams use both: rules bring in changing work, while manual groups add context that a filter cannot express clearly.
Do Jira structures replace boards?
No. Boards are useful for tracking work through a workflow, while structures emphasize hierarchy, relationships, and rollups. A team might use a board for daily task management and a structure to review how those tasks support epics or milestones.
How can I keep a structure easy to maintain?
Choose a clear purpose, assign an owner, and avoid unnecessary fields or rules. Review the structure regularly, especially after changes to projects, labels, workflows, or planning conventions. A smaller view that answers a specific question is often easier to trust than a single view containing every issue.
Conclusion
Jira Structures help teams create a flexible view of related work, especially when standard issue hierarchies or single-project boards do not show enough context. Start with a planning question, choose a clear hierarchy, and add rules and fields only when they help someone act.
When a structure becomes crowded or outdated, tighten its criteria and give someone responsibility for keeping it useful. That simple routine can turn a complex project view into a practical way to connect initiatives, epics, and day-to-day tasks.
If your project needs span workflows, reporting, deployment choices, or connected knowledge management, compare the structure approach with broader project platforms such as ONES.com. Choose the setup that helps your team see the work clearly and keep it moving.