Updated: Jan 4, 2020
How Jira hierarchies improve project management across teams.
It’s the one moment every member of any team dreads, yet has almost inevitably experienced: when someone responds to your quick question about a task with, I thought you were working on that? Cue awkward silence, panic, and a major interruption to the task you already had in progress.
When a project largely takes place within one team, Jira does an excellent job of preventing this. By having all tasks for a project sit on one dashboard, the whole team has a good level of visibility of the Jira issues and subtasks for the whole project. As well as knowing where responsibilities lie within the team, everyone involved also benefits from seeing the progress of a project as issues are moved to ‘done’.
But even in small companies, projects are rarely confined to one single team, or even one department. It poses a major challenge for project managers in particular: what happens when the projects you’re overseeing span across multiple teams?
When a project is cross-functional, how do you keep the same level of visibility and at-a-glance information that is so important?
Multi-level organisation — introducing Jira hierarchies.
When your challenge is tracking multiple projects across multiple teams, you’re already one step behind if your project management tool doesn’t reflect the way your teams work.
Jira is a highly customizable piece of software, but some may find its out-of-the-box structure limiting. When you’re managing a number of teams, you’re already juggling priorities and deadlines. You can’t afford to lose time switching from one dashboard to another to check on the progress of your projects.
This is when it’s time to look at introducing a multi-level Jira hierarchy. This way, you can structure your Jira instance to reflect the way your teams work — and more importantly, you can save time and improve your insights into the progress of your projects.
How multi-level Jira hierarchies give a better overview of your projects.
Grouping Jira issues allows you to gain an understanding of your progress.
Organize them in a Jira hierarchy view using directories. Drag and drop Jira epics, issues, and subtasks, or create new issues directly from the Panorama view.
Is your project manager stressing, always wondering if there are any critical issues still unassigned? Now you can group by priority and assignee, and see the answer immediately.
Grouping provides several useful insights for products managers. Group your Jira by version, priority, and status, and check if there are any important issues still open for a particular version.
Get multi-level insights that make a difference
How would you like to group your Jira tickets? By status, sprint, assignee, project, reporter or issue type? Multi-level hierarchy helps you manage multiple Jira epics, issues and subtasks using the criteria that work for you, meaning you can navigate straight to the information that matters to your project.
Use a multi-level Jira structure to get to the insights you need:
See the status of a project at a glance with progress bars that function across multiple teams Sum up all information under one hierarchy for efficient insights and reporting
Know exactly how many estimated work hours are remaining in a project, initiative or directory.
Easy Combo Moves for Advanced Jira Reporting
Get an aggregated value of reported time for each sprint (or feature, or issue) and then organize by priority.
Check how much time your team spent fighting bugs versus new features by simply grouping by issue type.
Group by “Resolution date” and issue type to see how your bugs to feature work has changed over time.
Combine “due date” and status, to highlight Jira issues with an approaching due date that are still not in progress.
When you’re managing projects across multiple teams, customizing Jira to align with your way of working should be your first step. It frees up time for you to focus on the real complexities of your job, instead of chasing information or struggling to balance multiple reports.
After all, when you spend less time trying to track down the right information, you’ll be able to use that time more efficiently. Start using that information and the insight it provides to improve your teams’ ways of working; the results across your teams will speak for themselves.
If you’re working with Jira you already know what a powerful tool it can be, thanks in part to the Atlassian Marketplace, which offers a huge range of applications to extend Jira’s functionality.
Panorama for Jira allows you to create projects that are structured the way you need them. Enhancing Jira by adding multi-level functionality, Panorama for Jira lets you structure work projects in hierarchies to easily track progress and find the information you need.