Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×We have components in both Service Desk and Jira software projects. We keep the component names in sync between the two projects. I'd like to see a dashboard to show ticket counts by component and project. However, when we do so, Jira is listing the component multiple times (once per project) on the dashboard. I'm assuming it is because it is consolidating by component ID instead of name. Is there a way to work around this and get each component name to list once?
Hi @Kenneth Hess,
I am Marlene from codefortynine.
I believe that the Jira standard gadget matches components by ID, which means it treats components from various projects as different entities.
Our app Quick Filters for Jira Dashboards matches field values by name. This makes it possible to create cross-project statistics with our app. We also provide a " Quick Two Dimensional Filter Statistics" gadget, which can do everything what the standard gadget can do, and more (like aggregating number fields, not only issues).
Hello @Kenneth Hess Welcome to the Community.
My multiple projects have same release version VH. By default in jira query I cannot list all the tickets under VH for all projects. Because the scope of a fix version is only under one project.
Therefore as a work around I use this jql: fixVersion ~ 'VH*'
Now this tilde symbol searches for regular keywords throughout all projects and lists the tickets with fix version VH.
I have to manually create the VH Fixversion across all of my projects. But once created, my jql gives my all the tickets.
Then I filter them in two dimensional gadget using Project title and count.
Maybe this technique can help solve your problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.