View Work across multiple Atlassian apps

[Tucker_ Kate]

My company uses several products across the Atlassian suite — primarily Jira Product Discovery (JPD) for product management and requirements tracking, and Jira Software for development work (to make it slightly more complicated we need to track two JIRA projects within different URL bases, but are part of the same company). We also have ad-hoc tasks our team works on that don't fit neatly into either tool that we need to track. Open to suggestions which tool we should track these in. 

What we're trying to achieve is a single, unified view showing all work assigned to each member of our team — across JPD, Jira, and any ad-hoc items — along with the current status of each piece of work, updated automatically so we always have the latest picture.

I've explored building a custom dashboard using the Atlassian REST API to pull this together, but before investing further in that route, I wanted to check:

1. Does Atlassian have a native feature or built-in view that provides this kind of cross-product team overview?
2. Is there a recommended approach within the Atlassian suite for consolidating work visibility across JPD and Jira in one place?
3. Are there any Atlassian Marketplace apps you would recommend for this use case?

I'd imagine this is a fairly common ask from teams using multiple Atlassian products, so I'd welcome any guidance on the intended solution or roadmap for this kind of cross-tool visibility.

Thank you for your help.

[Ivan Garcia _Appfire_]

Hi @Tucker_ Kate ,

Natively, Atlassian provides some ways to view cross-project data, such as using advanced JQL filters to pull issues from multiple projects into a single Jira dashboard. You can also use the "External Gadgets" feature or even Confluence as a central reporting hub to display information from different sources side-by-side. However, these native dashboards can sometimes feel a bit siloed when you need to connect data from entirely different Jira instances or maintain a truly synchronized real-time view across distinct products without constant manual switching.

If you are up for trying an app to help with this, I'd suggest our app Dashboard Hub. It is a great fit for this exact scenario because it acts as a central visualization hub for your organization's data. It allows you to create advanced dashboards that can combine and integrate different data sources, instances, and Atlassian products into a single reference point.

This means you can display Jira Product Discovery metrics right alongside Jira Software progress on the same screen, which is incredibly helpful for maintaining a "single source of truth" for your team.

Here are a few links that might be interesting!

Documentation: https://appfire.atlassian.net/wiki/spaces/RDD/overview
Marketplace: https://marketplace.atlassian.com/apps/1223898/dashboard-hub-for-jira-reports-charts
Support: https://apps.appf.re/support

I hope it helps,
Ivan from the Dashboard Hub team

[Jack Brickey]

Hi @Tucker_ Kate , I assume you have assesses the "Home" option and found that ot didn't meat your needs? You certainly can create a dashboard using the "currentuser()" JQL function in filters to illustrate work items associated with the logged in user. Also the Activity gadget is useful to illustrate the activities of the user.

[Laura Campbell]

Hi @Tucker_ Kate I'll just add that you mention the ad hoc tasks don't seem to fit into JPD projects or Jira Software. Have you tested a Jira Business project? It doesn't have all the software development features like sprint tracking and versions, and can be a good fit for non-software development task tracking.

[Rik de Valk _Brainboss_]

Hi @Tucker_ Kate , 

Having different Jira sites (different base-URLs) is far from ideal. 

I would highly recommend moving into a single Jira site, unless you have really strong reasons not to mix the two. But I haven't encountered much of such cases in all the years I've worked with the Atlassian ecosystem. 

You can have multiple Jira Product Discovery projects, multiple Jira projects and other Jira products in a single site. And you can govern access to these projects in ways that allow for segregation and restrictions in good ways. 

Once you have that, you can simply create insight by creating dashboards with queries such as @Jack Brickey recommends. 

Planning ad-hoc work can then also be done. Either in one of the Jira projects, or in a new separate Jira project (on the same site). 

You can read more about migrating data to another instance here: https://support.atlassian.com/organization-administration/docs/copy-product-data/ 

Have a nice day! 

Rik 

[Marlene Kegel - codefortynine]

Hi @Rik de Valk _Brainboss_ , welcome to the community, @Tucker_ Kate,

I am Marlene, working on the team who develops Deep Clone for Jira.

With the shift to cloud, I’m curious if more companies are starting to work across multiple Jira Cloud instances/sites. There could be several reasons or benefits for this (security, cost, or app management). For example, by splitting work across instances, you might only need premium features or specific apps on certain instances, which can reduce overall costs while still giving teams access to the features they need.

We also published an article with k15t on how to collaborate across cloud instances, definitely worth checking out if this topic interests you.

And another tip: if you ever migrate between Jira cloud instances, Deep Clone for Jira can make the process much simpler. :)