Skip to content

feat(atlassian): resolve dynamic scopes and index Confluence attachments - #7935

Merged
waleedlatif1 merged 3 commits into
stagingfrom
codex/atlassian-sync-scope
Sep 17, 2026
Merged

waleedlatif1 merged 3 commits into
stagingfrom
codex/atlassian-sync-scope

Conversation

@waleedlatif1

@waleedlatif1 waleedlatif1 commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Resolve Confluence and Jira All selections against the syncing account's current access. Preserve explicit selections and existing saved scopes; reject mixed All/explicit values before saving or querying.
  • Store large Confluence space audiences as bounded groups while preserving parent restrictions, reader identity, tenant isolation, freshness, and revocations.
  • Index PDF and Word attachments through the existing parsing pipeline with parent permissions, bounded downloads, and safe redirects. Missing attachment scope reports a partial sync while existing page connections keep working.
  • Update the connector guides. No schema migration is required.

Type of Change

  • Bug fix and feature improvement

Testing

  • 3,956 knowledge, search, connector, access, selector, credential, and processing regression tests passed after rebasing onto staging.
  • 95 disposable PostgreSQL tests passed, covering large audiences, concurrent revocations, cross-account isolation, large token queries, sync continuation, partition scheduling, and lifecycle locks. The 52 Confluence/access cases also run in both CI database provisioning variants.
  • Application type-check, full lint, all 46 repository audits (including API boundary validation), block registry, docs manifest, and migration checks passed.
  • Actual PDF and DOCX parser round trips are covered; live-provider attachment validation remains a deployment check.

Rollout: deploy the updated readers and prune protection, and drain old connector/directory runs before starting the new audience writers. App-before-worker promotion alone does not stop already-running old jobs from pruning the new audience records. Attachment indexing requires the documented attachment scope; previously saved selection snapshots require reselecting All to become dynamic.

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercel Bot commented Sep 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Sep 17, 2026 7:50pm UTC

Request Review

@greptile-apps

greptile-apps Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 4/5

The PR is not yet safe to merge because ambiguous Google 403 responses can conceal connector-wide credential or scope failures behind indefinite per-user retries.

Summary

This PR expands Atlassian connector behavior with dynamic “All” scopes, Confluence attachment indexing, bounded audience groups, and associated access-control and sync changes. Changes added since the previous review also introduce durable per-user Google connector scheduling, document-processing queue lanes, stricter durable secret-provenance enforcement, and supporting database and CI coverage.

  • Resolves dynamic Jira and Confluence scopes against current provider access.
  • Indexes supported Confluence attachments while inheriting parent permissions and preserving partial-sync safety.
  • Adds durable connector partition work and per-user Google crawl scheduling.
  • Separates interactive and backfill document-processing queues.
  • Extends tests, documentation, schema metadata, and PostgreSQL integration coverage.
Diagram
%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Directory discovery] --> B[Durable per-user partitions]
  B --> C[Content listing]
  B --> D[Permission refresh]
  C --> E{Provider result}
  D --> E
  E -->|Success| F[Commit cursor and documents]
  E -->|Known user-specific 403| G[Defer partition with retry]
  E -->|Connector-wide failure| H[Surface connector error]
  F --> I{All partitions complete?}
  G --> I
  I -->|No| B
  I -->|Yes and safe| J[Reconcile removals]
Loading

Reviews (4) · Last reviewed commit: "fix(ci): isolate Confluence migration te..."

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 45 files

Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Fix all with cubic | Re-trigger cubic

Comment thread apps/sim/lib/knowledge/connectors/sync-engine.ts
Comment thread apps/sim/connectors/jira/meta.ts
Comment thread apps/sim/lib/knowledge/access/group-membership.integration.ts
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

Comment thread .github/workflows/test-build.yml
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 48 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic

@waleedlatif1
waleedlatif1 force-pushed the codex/atlassian-sync-scope branch from 7e38379 to b803a36 Compare September 17, 2026 19:48
@waleedlatif1
waleedlatif1 merged commit 0b893d7 into staging Sep 17, 2026
20 of 22 checks passed
@waleedlatif1
waleedlatif1 deleted the codex/atlassian-sync-scope branch September 17, 2026 19:48
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cubic-dev-ai review this PR

@cubic-dev-ai

cubic-dev-ai Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 48 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Tip: cubic can generate docs of your entire codebase and keep them up to date. Try it here.

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant