Comparison
Side-by-side comparison
Compare up to three connection records. “Not verified” or “Not confirmed” means the detail has not been documented in the sources we reviewed — never that it is unavailable. Records are reviewed against official documentation, not hands-on tested.
| Attribute | Atlassian (Jira and Confluence) on Gemini |
|---|---|
| Availability | Verified available |
| Connection type | Two separate Google Cloud connectors for Gemini Enterprise — Jira Cloud and Confluence Cloud — not a single Atlassian connector and not a connected app in the Gemini app |
| Capabilities |
|
| Setup method | Separate Gemini Enterprise Jira Cloud and Confluence Cloud data stores, each configured by an administrator |
| Admin involvement | Required for each connector separately. An administrator creates and authorizes a Jira Cloud data store and, independently, a Confluence Cloud data store inside a Gemini Enterprise app; there is no user-level toggle in the Gemini app and enabling one does not enable the other. |
| Limitations | Google documents Jira Cloud and Confluence Cloud as two separate Gemini Enterprise connectors; there is no single combined Atlassian or Rovo connector, so a site missing one connection will not surface that product's content.; This is a Gemini Enterprise connector; Google does not document Jira or Confluence as connected apps in the Gemini app at gemini.google.com.; Neither connector documents a delete action for issues, pages, projects or spaces.; Available actions depend on what an administrator enables per connector, so end users may see a narrower set than Google's full documented list for either product. |
| Documentation review | Verification status: Review overdue — The scheduled documentation review date has passed (or, without a schedule, the last review is over 90 days old). Re-check the official source before relying on details. Last reviewed 9 Sept 2026 Next review 9 Oct 2026 |