Bubbles Documentation
Effective date: May 5, 2026
Bubbles - AI Risk & Dependency Dashboard for Jira (“the App”) is provided by Moose AI LLC.
This documentation explains how to get started with the App, what the main dashboard views show, and how teams can use Bubbles to understand project risk, blockers, and dependencies inside Jira.
Overview
Bubbles helps Jira teams visualize project risk, blockers, and internal or cross-project dependencies using interactive bubble maps and AI-assisted dependency insights.
The App is designed for technical program managers, program leads, product leads, engineering managers, and Jira teams that need clearer visibility into delivery risk, upstream and downstream blockers, and portfolio-level dependency health.
Getting Started
After the App is installed, open Bubbles from Jira’s Apps menu.
The App analyzes Jira project and issue metadata available to the installing Jira site and displays dependency and risk information in visual dashboard views.
To begin using the App:
Open Bubbles from Jira.
Select or review seed projects.
Use the Dependency Graph to view cross-project relationships.
Switch to Risk Heatmap to identify higher-risk projects.
Drill into Level 1 to inspect execution risk and issue-level contributors.
Seed Projects
Seed projects are the projects selected by the user as the starting point for dependency and risk analysis.
Bubbles uses seed projects to build the main dashboard view and discover related neighbor projects through Jira links and AI-assisted dependency signals.
Neighbor Projects
Neighbor projects are related projects that may have upstream or downstream dependency relationships with selected seed projects.
Neighbor projects may be discovered through Jira issue links, dependency signals, or AI-assisted relationship analysis.
Dependency Graph
The Dependency Graph shows selected seed projects and auto-discovered neighboring Jira projects in an interactive map.
This view helps teams understand which projects are connected through Jira issue links or AI-assisted dependency signals.
In this view:
Seed projects are projects selected by the user.
Neighbor projects are related projects discovered through dependency signals.
Solid arrows represent Jira-linked dependencies.
Dashed arrows represent AI-inferred dependency signals.
Bubble details may show counts such as epics, blocked issues, Jira links, and AI signals.
Use the Dependency Graph to understand cross-project relationships and identify where blockers or dependency signals may exist.
Risk Heatmap
The Risk Heatmap helps teams identify high-risk seed projects and dependency pressure.
Risk scores are shown on a 1–5 scale, where higher scores indicate higher dependency or execution risk.
Risk signals may include:
Upstream blockers
Blocking edges
Blocked issues
Priority
Due dates
Issue status
Other Jira metadata available to the App
Use this view to quickly identify projects that may need attention before execution risk spreads.
Level 1 Drilldown
Level 1 Drilldown provides a deeper project-level view of execution risk.
This view helps teams understand how external blockers, internal epic risk, and blocked issue counts contribute to project execution risk.
Level 1 may show:
Upstream projects that block the selected project
Downstream projects impacted by the selected project
Internal epics
External blocked issue counts
Internal blocked issue counts
Execution risk scoring signals
Risk contributors and dependency context
Use Level 1 when you need to move from portfolio-level visibility into project-level execution risk.
AI-Assisted Dependency Signals
Bubbles may use AI-assisted signals to identify possible relationships between projects or issues that are not explicitly linked in Jira.
AI-assisted signals are intended to help teams discover potential dependency risk. These signals should be reviewed alongside Jira issue details, team context, and existing delivery processes.
AI-assisted signals are not intended to replace team judgment, Jira workflows, or formal program management processes.
Jira Data Used
The App may use Jira project and issue metadata only as needed to provide App functionality.
This may include:
Project information
Issue and epic metadata
Dependency relationships
Issue status
Issue type
Priority
Due dates
Assignee account references
Labels
Components
Parent or epic relationships
Issue links
Updated timestamps
Related project or issue metadata
The App uses this information to provide dependency visualization, risk analysis, AI-assisted dependency signals, caching, troubleshooting, reliability, and security.
Permissions
Bubbles runs within Atlassian Forge and uses Atlassian app permissions to access Jira data required for App functionality.
The App respects Jira permissions and the data available to the installing Atlassian site.
Customer access controls, Jira permissions, user management, and data deletion may also be controlled by the customer’s Atlassian organization and Jira administrators.
External Processing
The App may process limited Jira project and issue metadata through an external embeddings service hosted on Google Cloud Run in the United States.
This service is used to generate vector embeddings for AI-assisted dependency and risk insights.
The embeddings service is intended only for internal App functionality and is protected by API-key authentication.
Caching and Performance
The App may temporarily cache data to improve performance, reliability, and dashboard responsiveness.
Caching is used to support dependency visualization, risk analysis, AI-assisted dependency signals, troubleshooting, and operational reliability.
Troubleshooting
If the App does not load or expected projects are missing, try the following:
Confirm the App is installed and enabled.
Confirm the user has access to the relevant Jira projects and issues.
Refresh the App data.
Check whether the relevant Jira projects contain linked issues, epics, or recent issue activity.
Confirm that Jira permissions allow the user to view the relevant projects and issues.
Contact support if the issue continues.
Support
For App support, contact:
Please include a description of the issue, the affected Jira site or project if applicable, steps to reproduce the issue, and any relevant screenshots or error messages.
Please do not include sensitive customer data unless necessary to explain the issue.
Security
To report a security issue or vulnerability, contact:
Please include a description of the issue, steps to reproduce it, the affected app or environment, and any relevant screenshots, logs, or technical details.
Privacy and Security
Privacy Policy:
https://privacy.mooseai.co
Security Policy:
https://security.mooseai.co/
Language Support
The App currently supports English.
Updates
We may update this documentation from time to time. Updates will be reflected by a revised effective date.
Contact
Moose AI LLC
General support: support@mooseai.co
Security: security@mooseai.co