nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pulling core fields into JIRA Dashboard Gadgets - why not all fields can be pulled?

Alexandra Keogan

Hi all

We have a JIRA "project" setup (our Product Backlog) comprised of multiple teams working on the same Product. These teams were setup using out of the box Advanced Roadmaps functions (Plans > View Shared Teams > Create Team).

We wanted to use gadgets from the "Dashboards" functions e.g. Two Dimensional Filter Statistics and noticed that this "Team" field could not be pulled. We were informed by our Global Support team that this had been escalated to Atlassian and they said this could not be done / there was no solution for this.

This seems odd - what is the point of having Dashboards and Gadgets if we cannot pull core fields to get basic metrics?, in this case metrics related to Teams contributing to the same product?.

Has anybody found similar issues and was anyone able to get this resolved?

Comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

It's usually quite a simple reason - the fields are utterly useless as data points.

The two dimensional filter gadget is a great point in case - a lot of the fields you could define for it would result in completely useless reports.

But I prefer to explain with the pie-chart gadget, it's much more simple. It does not support text fields because the display would be utterly useless. You have to assume that each entry on each issue is unique, otherwise you're working with astronomical numbers that humans certainly can't comprehend. So for a text field, you can't do anything other than "one slice per issue", which is useless as a report.

It's similar for other fields.

The only ones you can really work with are "bounded" lists - you need select lists, or multi-select lists where you can reliably count the entries.

Aron Gombas _Midori_

On the implementation level, only a small subset of the custom field types can be used as report dimensions. The "team" field, for example, isn't.

You could maybe use a simple select field custom field instead, that would also work with the 2D gadget.

Hannes Obweger - JXL for Jira

Hi @Alexandra Keogan

if you're open to solutions from the Atlassian Marketplace, the you should be able to create the views you're looking for in 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, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including the ability to group your issue by any issue field(s) - of course, including the Team field - as well as to calculate sum-ups across these groups. With these, you can create a view like this in just a couple of clicks:

Note that you can view, sum-up, and group by any issue fields(s), and also configure different sum-up techniques (like e.g. the average). As you can see above, you can also directly interact with the underlying issues and update them individually or in bulk (using copy/paste).

I should add that JXL doesn't currently have a dashboard gadget (however will have one soon) - but many of our customers simply use JXL sheets as "de-facto dashboards".

Any questions just let me know,

Best,

Hannes

Alexandra Keogan

The Team field we're using is not customized it is used directly from the Advanced Roadmaps feature > Teams > Create Teams.

Judging from everyone's comments this is not possible unless additional plugins are purchased from the Market Place

Nic Brough -Adaptavist-

There is a feature request to get the "teams" field to work as a regular select list in searches and gadgets.

Welcome!

It looks like you're new here. Sign in or register to get started.