Organize Queues by Content?

[Jason Sadler]

We're beta-testing our platform and receiving a lot of feedback from beta-testers in the Queues section. I am keeping an eye on this portal and assigning the testers' feedback to our product manager. I'm worried that as we scale and start getting more feedback, the influx of issues will become overwhelming. Thus, I'd like to be able to thematically group feedback into something like a folder. 

I've asked this before and done some research on it, and it seems like using components and custom JQL filters could be one way to do this. However, I have not figured out the exact steps for doing those things. Can someone please lay those out for me or offer an alternative?

[Jack Brickey · Accepted solution]

Hi @Jason Sadler , can you provide an example of a theme? As you have discovered there is not the concept of folders with queues inside the folders natively. You could certainly use components to qualify your queues. For example let's say you want to break "all open" into three sub-queues: operations, engineering , HR. You could do the following:

1. create three components: operations, engineering , and HR
2. you would then create three queues naming them appropriately and use a JQL like this - resolution is empty and components = operations...

now, keep in mind that Components is multi-select which could result in issues appearing in more than one queue if it has multiple components. For this reason you may wish to leverage a single-select custom field rather than Components.

[Alex Ortiz · Accepted solution]

@Jason Sadler 

Queues are super flexible. They each have a JQL section that basically allows you control which requests show up in which queue.  All you need to do is edit your queue (or make a new one) and base it off whatever field you want.  This can be your component or it can be a custom field, or any other field in Jira.  

Then only the requests that match the criteria for your queue will be displayed.

[Hannes Obweger - JXL for Jira · Accepted solution]

Hi @Jason Sadler

as already mentioned, the easiest might be to create separate queues, with respective JQL statements.

Alternatively, if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields - including all JSM-specific fields - much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

With these, you can build a view like e.g. this in just a couple of clicks:

This is really just one of a virtually endless number of possible views and reports; you can also view and group by any other issue fields, configure different sum-up styles, etc. etc.

As every JXL sheet is powered by a JQL statement, so you can easily model queues through JXL sheets - many of our customers already do so. Another advantage is that JXL would allow cross-project queues, if that's something that might be relevant to you.

Any questions just let me know,

Best,

Hannes