[EazyBI Jira 7] Why a dimension cannot be both in "page" and "row/column" zone?


Everything is in the title: Why a dimension  cannot be  both in "page" and "row/column" zone?

It sounds pretty useful to have a dimension used in the same time as a filter and row/column label.

I do it by using the dimension in row/column and then filtering (regexp), but for dashboards it's not really user friendly.

Any insight? 

4 answers

Hi Jerome, 

Currently, this is an eazyBI design decision that a dimension can be placed only once in Pages, Rows or Columns.

We are thinking about how to improve change of row and column selection in dashboards (similar to common dashboard pages selection).

Could you share most common use cases (which dimensions) when you would like to select the same dimension selected in Rows or Pages also as a Page selection?

Currently, you can select Project dimension in Pages and display Issue dimension Project level members in rows.

Ilze, support@eazybi.com


Hi Ilze,

I have to very common use cases.

I'm managing several development departments (calculated member) so I want to be able to see by department and by developer. So I'll need to be able to filter by a set of developers but still have the data organized and displayed by developer also (the logged by dimension will be then both in "pages" and "rows"). Lately I've created an analysis to track planned vs actual time spent at issue level. Not being able to have it "grouped" by developer was painful due to the number of issues. I have tons of reports based on developer dimension (injection rate, reporting ratio, time ratios, etc.) it's one of my mains analysis axis.

An other  use case is that we need to track activities by project code name (it's a custom dimension). Then we need to be able to group code names by business unites we have (calculated member). So here in "pages" we have one or several BU selected then in rows we need to see data grouped by "project code".

As described above it mostly looks like we need a "group by" feature.

Let me know if you need further details.


Hi Jerome, 

thank you for the answer!


If developers belong to a particular JIRA user group (or several groups dedicated to group developers), you could import and use "Logged by Group" dimension in Pages and "Logged by" dimension in rows, with enabled "nonempty" option. Then only values for Logged by users belonging to selected JIRA user group(s), would be displayed in the report.


For Busines units, probably you could precalculate "Business unit" as an additional custom field (based on Project code field information) and import it as a separate dimension using Advanced settings. Precalculation could be done during data import using JavaScript calculated custom fields or directly in JIRA using JIRA Misc scripted fields. Then you could select "Business unit" dimension in Pages and "Project code" dimension in Rows (again, together with nonempty option) - then only values for Project codes from selected Busines unit would be displayed in the report.


For more detailed information, please contact support@eazyBI.com .



eazyBI Customer Support Consultant

Hi Ilze,

Understood, several tricks can do the job, thank you for giving me hints on how to do it. Nevertheless from my user perspective this limitation is not productive, it would be more intuitive and simpler to "page" by any used or unused dimension.

Thanks anyway!


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,296 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot