GML-2211: Jira Cloud Data Source Connector - #68
Open
prinskumar-tigergraph wants to merge 16 commits into
Open
prinskumar-tigergraph wants to merge 16 commits into
prinskumar-tigergraph wants to merge 16 commits into
Conversation
added 2 commits
September 30, 2026 14:07
- Jira Cloud REST API client with retry, rate-limit handling, and parallel comment fetching (up to 10 concurrent threads) - Pydantic config models: connection, scope, sync state - ADF → Markdown converter for issue descriptions and comments - Deterministic mapper: JiraIssue, JiraComment, JiraUser, JiraProject vertices + edges; comments chunked directly (bypass ECC Document pipeline) - Log-output filter strips stack traces / log lines from comments before chunking to reduce noise in search results - Sync orchestration: incremental JQL checkpoint, content-hash dedup, batch document loading (every 10 pages), pipelined page fetch, crash-recovery rebuild detection (_has_unprocessed_chunks) - REST endpoints for data source CRUD, sync trigger, schema install - UI: DataSourcesConfig page, Rebuild dialog live sync-status guard - ECC: zero-text guard skips empty chunks before embedding - ECC util: register jira / jira_comment chunker types - Prompt fix: map Jira ticket keys to schema attributes (not vertex IDs) - Embedding store: transient-error retry with exponential back-off - Tests: connector unit tests, cypher generation, structural validation - Design doc: docs/design/jira-data-source-connector.md - Example config: docs/tutorials/configs/graph_configs/data_sources.json - .gitignore: exclude configs/graph_configs/*/data_sources.json (credentials)
prinskumar-tigergraph
force-pushed
the
GML-2211-feature-jira-source-connector
branch
from
September 30, 2026 08:47
0538732 to
4cd4c80
Compare
added 7 commits
September 30, 2026 14:46
… ticket query behavior
…lts (configurable via UI)
…FSET instead of unsupported getVertices offset param
…TY edges - Switch embedding model to gemini-embedding-2 (fixes 500/503 transient errors) - Bump default_concurrency to 5 (embed_sem=10 concurrent embeddings) - workers.py: look up Document's CONTAINS_ENTITY edge to get correct JiraIssue vertex ID for chunk edges (fixes jira:issue:207120 → jira:gml-2191:issue) - DataSourcesConfig.tsx: poll rebuild_status live during ECC build, show 'Processing documents (X/Y — Z%)' instead of static 'build started' - client.py: bulk-fetch changelogs for all issues in one POST per page - mapper.py: include status/changelog history in issue document text - sync.py: reconcile comment chunks, recovery build on missing embeddings
prinskumar-tigergraph
force-pushed
the
GML-2211-feature-jira-source-connector
branch
from
October 1, 2026 12:36
770024f to
39a5fcf
Compare
added 6 commits
October 1, 2026 19:55
…comments in workers.py
…for all LLM output formats
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
Adds a first-class Jira Cloud integration to the GraphRAG pipeline, enabling Jira issues and comments to be automatically ingested, chunked, embedded, and searched through the knowledge graph.
What's included:
Testing:
Unit tests for connector, comment chunking, cypher generation, and structural validation