With TISSUE - Linked Issues Table Gadget how to add dynamic filter in Dashboard?

[Jérôme Godbout]

Is there a way to select dynamic filter (like project) to Tissue table? I want the Tissue table since it's the only one that display multiple childs linked issues to a given issues and that's what I need (I do not need the one line one issue table that all the dynamic filter comes with).

I just want to avoid copying the dashboard and changing the project filter over and over again. Why can't we just have a filter that apply to the whole board gadget in a dynamic way?

I DO NOT want a filter plugin that limited to his basic widget display, I need it to filter the issues and I could either inject it into the JQL of Tissue or if the display support multiple sub entry for the linked issues and expand those with property display like tissues does that could be good. Ideally I need a matrix of issue  of certain type in row and other issue type in columns and mark with a X where they are linked with a particular link type. But This seems rather impossible or at least could not found anything that display in matrix between different issues.

                            |   Task1  |    Task 2 | Task 3 ...

-------------------------------------------------

Requirement1  |                 |      Y      |      Y

Requirement2 |       Y        |              |

That would be the best, Tissue is the nearest who give me multiple row (ugly but at least got some information:

Requirements 1  |   Task 2 

                                Task 3

Requirements 2 |  Task 1   

But I have to make one dashboard per project, for a service cie with every clients has his own project, that make too many dashboard to maintain and create. Any body have an idea or a solution for this?

[Valerie Knapp]

Hi @Jérôme Godbout , welcome to the Atlassian Community and thanks for your question.

In order to get dynamic filters on a Jira dashboards, you can't do anything out of the box. You will need to get an app. 

Several of my customers use eazybi for this type of use case. You can see here, for example, https://eazybi.com/accounts/1000/dashboards/14871-chart-types , where they have made available some sample reports / dashboards, where you can filter by different variables, such as project, issue type, Sprint, etc. 

If you want more information, please reach out to the vendor https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira who can provide a demo and answer any questions you might have about feasibility. 

Cheers

[Jérôme Godbout]

The problem with easybi the results need to be into the easybi widgets, and the table fall short to display 2d issues, it's only issue versus a metric, I need matrix of relationship of issues in a axis and related other issue into the other axis. Tissue is not great but it's the only that can do something that come close to it but is far from being good.

[Oskars Laganovskis]

Hi @Jérôme Godbout ,

If each task is only related to one Requirement, you might build a custom Issue hierarchy based on issue links. You might read more about that here - Additional issue hierarchies .

While doing that, you can also import separate hierarchy levels as dimensions.

That way, you get different issue types in separate dimensions.

You might then put one hierarchy level on rows and another hierarchy level on columns and use a measure to indicate their relations.

However, that is not the recommended approach as it creates an excessive background dataset, leading to slower report execution and possible problems on larger instances.

Displaying several expanded hierarchy levels on rows is considered a better option.

If you want to strictly limit the data visible to different users of the same dashboard, you might use the Data access role functionality in eazyBI.

Please read more about that here - Data access roles.

You might define different data access roles for users or user groups and limit the projects visible to them. This way, they will only see what they are entitled to see.

Then, you will only have to maintain the user allocation to Jira user groups instead of having a separate Jira dashboard for each Project.

Regards,

Oskars / eazyBI support

[Jérôme Godbout]

Hi, sadly it's a n to n relationship, not a 1 to 1. Therefore the matrix view needed to keep track everything is well covered.

[Oskars Laganovskis]

In that case, it would also be possible to import these issue links as dimensions without building a hierarchy.

Then, you might use the "Issue" dimension together with the imported Issue link dimension.

The "Project" filter would apply to the "Issue" dimension members.

However, that setup has the risk of excessive background dataset which might lead to calculation timeouts or out-of-memory errors.

Please contact eazyBI support directly with as many details as possible about the existing issue relation setup and your reporting requirements to find the best-fitting solution for you.

Oskars / eazyBI support