Issues  |  Knowledge Base

ALM Works

  • Products|
  • Download|
  • Pricing|
  • Support|
  • Company
ALM Works Business Continuity During the COVID-19 Outbreak
  • Structure
  • Structure helps Atlassian's largest customers track, manage, and visualize progress across Jira projects
    • Try It
  • Structure Overview
  • Atlassian Marketplace
  • Structure.Gantt
  • Add the power of Gantt charts to Jira projects
  • Structure.Gantt Overview
  • Atlassian Marketplace
  • Structure.Pages
  • The Ultimate Jira-Confluence Collaboration Tool
  • Structure.Pages Overview
  • Atlassian Marketplace
  • Structure.Testy
  • Test checklists extension for Structure
  • Structure.Testy Overview
  • Atlassian Marketplace
  • Colors for Jira
  • JQL-based color highlighting for enhanced issue navigation.
  • Client for Jira
  • Now an open source product!
    Interactive desktop client for Jira. Available via open source or as a free product.
  • Structure Version: 6.5.2 Feb 23, 2021
  • Free 30-Day Trial
  • Download Archive
  • Structure.Gantt Version: 2.7 Dec 7, 2020
  • Free 30-Day Trial
  • Download Archive
  • Structure.Pages Version: 1.6 Feb 1, 2021
  • Free 30-Day Trial
  • Download Archive
  • Structure.Testy Version: 2.5 Feb 3, 2020
  • Free 30-Day Trial
  • Download Archive
  • Colors for Jira
  • Version: 2.1.1 Sep 25, 2017
  • Free 30-Day Trial
  • Download Archive
  • Client for Jira
  • Version: 3.8.4 Aug 21, 2017
  • Free Version
  • Download Archive
  • Structure
  • Choose your platform:
  • Cloud Pricing
  • Server Pricing
  • Data Center Pricing
  • Structure.Gantt
  • Choose your platform:
  • Cloud Pricing
  • Server Pricing
  • Data Center Pricing
  • Structure.Pages
  • Choose your platform:
  • Server Pricing
  • Data Center Pricing
  • Colors for Jira
  • Choose your platform:
  • Server Pricing
  • Structure
    • Support Request
    • Documentation
    • Suggest an Idea
    • FAQ
    • Training
  • Structure.Gantt
    • Support Request
    • Documentation
    • Quick Start Guide
  • Structure.Pages
    • Support Request
    • Documentation
  • Structure.Testy
    • Support Request
    • Documentation
  • Colors for Jira
  • Support Request
  • Documentation
  • Client for Jira
  • Support Request
  • Documentation
  • FAQ
  • Knowledge Base
  • Contact support by e-mail
  • Support Description & SLA
  • About Us
  • Our Customers
  • Partners & Resellers
  • Contacts
  • Join Our Team!
  • News and Press Releases
  • Press Kit
  • Blog
  • Events
Call sales: +1 617 600 4369
  • info@almworks.com
  • sales@almworks.com
  • ALM Works, Inc.
  • 181 Wells Ave., Suite 204
    Newton, MA 02459
    USA
  • ALM Works Ltd.
  • Times Center, Suite 214
    Kantemirovskaya Str., 2A
    Saint Petersburg
    Russia 197342
  • Company
    • ALM Works Blog
    • Prioritized JIRA backlogs without Agile

Prioritized JIRA backlogs without Agile

By Robert Leitch on May 26, 2015

Not using JIRA Agile, but still want prioritized backlogs? Structure them instead.

Backlogs aren't exclusive to Agile. We all have them, and we all need to prioritize them.

You're a project manager and you want your developers to tackle their JIRA issues in a specific order.

You're not using the JIRA Agile plugin, so how do you maintain an ordered backlog?

Pure JIRA Backlog

One solution is to prioritize issues in JIRA by specifying a 'backlog priority' in a custom number field, then sorting issues by that field in the JIRA issue search page.

Developers can view their own prioritized JIRA backlogs with a simple JQL query:

JQL query
assignee = currentUser() AND resolution = Unresolved ORDER BY "Backlog Priority" DESC

Reordering issues using this method is not so simple. It entails opening each issue to edit the priority field, and requires some number juggling to get issues in the right place.

Structured JIRA Backlog

There's a neater way to do it using the Structure plugin. Simply make a list of issues in a structure for your developer and drag-and-drop them into the order you want them done in. It's as simple as that.

Drag, drop

Drag, drop, done

Anyone else viewing this structure will see its issues laid out in exactly the same order as you put them in.

Even if they have the backlog structure open in another browser while you're moving issues around in it, they will see it update automatically with the changes you make.

This is too straightforward for my liking, so let's spice it up a bit.

I don't want anyone else to prioritize tasks in the backlog

No problem, just make yourself the owner of the backlog structure and set its permissions to 'View' for 'Everyone'. This makes it read-only for everyone except you (and JIRA admins, who always have full permissions over structures).

I want a prioritized team backlog

Configure a Filter Synchronizer to automatically pull in issues assigned to any of the team members. The query would look something like this:

JQL query
assignee in (albert,rleitch,Harry,Jack,John)

Now drag and drop to prioritize. Naturally, you can also use the Filter Synchronizer for individual backlogs.

I want a prioritized team backlog with issues grouped by assignee

Create a meta-issue (container) for each of your team members. You can add a Filter synchronizer for each team member that will automatically insert their issues in the corresponding container (and move them when issues are reassigned).

In Structure 3.0 [update: Structure 3.0 public beta is out!] you'll be able to do this kind of grouping automatically, and you'll even be able to reassign issues just by dragging them to another team member's container. But for now you'll have to make do with synchronizers.

I want a single backlog for multiple teams

Here's a bonus post about using Structure to define teams in JIRA Agile that describes how to do just that, and is equally applicable for non-Agile teams. It also shows how to reproduce each team's backlog in a separate structure.

When you create multi-level backlogs like this, remember that Structure rank (the order of issues within a structure) is not global. If you reproduce different levels of this backlog in other structures, (e.g. individual teams, personal backlogs) then you'll need to decide where exactly to rank them.

The great news is that Structure 3.0 will allow structures to contain other structures. Which means that a multiple team backlog can be composed of separate team backlog structures, which can be composed of personal developer backlog structures. Which means that changes made to rank in any of those structures will be reflected at all levels.

Found something Structure doesn't do, but should? Tell us about it in our Structure UserVoice forum. Questions about this post are welcome in the comments below.

Tags: Structure, backlogs, prioritizing JIRA issues, JIRA Agile, noagile
Tweet
Structure

Hierarchical issues for great project management in Jira

JIRA Client

Desktop client for Jira

Structure plugin on the Atlassian Marketplace
Our Customers
  • logo
  • logo
  • logo
  • logo
Newsletter & Updates
Recent Tweets
Tweets by @almworks
Products
  • Deliver
  • Structure
  • Structure.Gantt
  • Structure.Pages
  • Structure.Testy
  • Colors for Jira
  • Client for Jira
  • Deskzilla
Resources
  • Documentation
  • Marketplace
  • Latest News
  • Blog
  • Support SLA
  • Legal
Company
  • About ALM Works
  • Customers
  • Contacts
  • Join our Team!
Quick Links
  • Customer Portal
  • Partner Portal
  • For Partners & Resellers
  • For Press
Site Map
Call Sales: +1 617 600 4369
info@almworks.com sales@almworks.com
Copyright © 2004-2021 ALM Works, Inc. All Rights Reserved.|Privacy Policy|Terms of Use