Skip to content

feat: add Front conversation issue integration#715

Open
jaeyunha wants to merge 5 commits into
stagingfrom
issue-577-p1-front-create-link-issues-from-c
Open

feat: add Front conversation issue integration#715
jaeyunha wants to merge 5 commits into
stagingfrom
issue-577-p1-front-create-link-issues-from-c

Conversation

@jaeyunha

Copy link
Copy Markdown
Member

Summary

  • add Front integration setup/disconnect plus signed sidebar endpoints for issue search/create/link/unlink
  • persist Front conversation links as provider source metadata and expose linked source backlinks on issue details
  • queue Front follow-up jobs to post an internal note and reopen conversations when linked issues complete or cancel
  • repair integration settings Front/Zendesk setup forms after branch sync and add focused UI/unit coverage

Verification

  • pnpm exec vitest run tests/integrations-view.test.tsx
  • pnpm exec biome check apps/web/src/app/(app)/settings/integrations/page.tsx apps/web/tests/integrations-view.test.tsx
  • make check attempted; blocked at typecheck by pre-existing missing web deps (drizzle-orm, better-auth, @better-auth/passkey)
  • go test ./internal/integrations attempted; blocked because go is not installed in this runner

Notes

jaeyunha and others added 5 commits June 15, 2026 20:39
- SSRF: replace unvalidated frontAPIBaseURL with normalizeFrontBaseURL
  that requires https and a .frontapp.com host on admin-supplied values
- HTTP client timeout: pass 10s-timeout client to validateFrontToken
  instead of http.DefaultClient (no timeout)
- Dead branch: failFrontJob now sets status "error" (not "degraded") on
  401/403 permission failures so operators know the token needs rotation
- FrontIssueCreate: distinguish validation sentinels (400) from DB/infra
  errors (500) via isFrontValidationError helper
- frontIssueDescriptionHTML: build combined HTML first, call
  sanitizehtml.RichText once instead of twice

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@jaeyunha

Copy link
Copy Markdown
Member Author

Controller disposition for current head b34a356: validation-blocked / rebase required; do not merge as-is.

Evidence:

  • PR feat: add Front conversation issue integration #715 targets staging but does not contain current origin/staging; GitHub reports mergeable=CONFLICTING.
  • Merge simulation conflicts across integration startup/router/catalog files, front.go, handler_test.go, issue source-link handling, and generated OpenAPI/SDK.
  • Branch includes stale P1 Front: create/link issues from conversations and reopen on resolution #577 history plus the newer hardening/setup-form commits; the intended delta needs to be ported onto current staging cleanly.
  • Lane report says focused Front integrations-view Vitest and Biome passed, but make check/Go validation were blocked in-lane; no GitHub checks are reported.

Required path:

  • Rebase/port the Front hardening/setup-form delta onto current origin/staging, preserve already-landed Salesforce/Jira/Zendesk/Gong/Sentry source-link changes during conflict resolution, regenerate OpenAPI/SDK from current contract, then rerun focused Go + web + SDK gates before merge.

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