How nopleasenorbi/linksphere works
LinkSphere syncs Jira issues, users, and related Confluence pages into a Neo4j knowledge graph, then presents project- and user-focused interactive views. Users configure Atlassian credentials, select or refresh projects, and explore graph data through filters, search, and node details. The backend route/controller/model chain and Jira ingestion calls are visible in excerpts; several frontend-to-API links and documented graph interactions are based on the README because the relevant page request code was not excerpted.
Main entry points: App.js App router · jiraController.js Jira controller · jiraRoutes.js Jira routes · databaseRoutes.js Database routes
Components 23
Web interface
- App router
frontend/src/App.js - Navigation
frontend/src/components/NavigationBar.js - Atlassian settings
frontend/src/pages/Settings.js - Project list
frontend/src/pages/Projects.js - Project graph
frontend/src/pages/Projectgraph.js - User list
frontend/src/pages/Users.js - User graph
frontend/src/pages/UserGraph.js - Info pages
frontend/src/pages
Backend API
- Express server
backend/server.js - Jira routes
backend/routes/jiraRoutes.js - Database routes
backend/routes/databaseRoutes.js - Database controller
backend/controllers/databaseController.js
Atlassian sync
- Jira controller
backend/controllers/jiraController.js - Credential store
backend/models/jiraCredentials.js - Atlassian client
backend/utils/atlassianClient.js - Issue fetcher
backend/utils/fetchAllProjectIssues.js - Page fetcher
backend/utils/fetchConfluencePages.js - Graph transformer
backend/utils/transformJiraDataToGraph.js - PostgreSQL
Graph storage
- Graph queries and writes
backend/models/graphModel.js - Neo4j graph store
Other components
- Team user
- Atlassian APIs
Connections 30
- Team user → App router: uses
README.md - App router → Navigation: renders
frontend/src/App.js - App router → Info pages: routes to
frontend/src/App.js - App router → Atlassian settings: routes to
frontend/src/App.js - App router → Project list: routes to
frontend/src/App.js - App router → Project graph: routes to
frontend/src/App.js - App router → User list: routes to
frontend/src/App.js - App router → User graph: routes to
frontend/src/App.js - Atlassian settings → Jira routes: configures via API
README.md - Project list → Jira routes: loads projects
README.md - Project list → Jira routes: requests refresh
README.md - Project graph → Database routes: loads graph data
README.md - User list → Database routes: loads users
README.md - User graph → Database routes: loads user graph
README.md - Express server → Jira routes: mounts
backend/server.js - Express server → Database routes: mounts
backend/server.js - Jira routes → Jira controller: dispatches
backend/routes/jiraRoutes.js - Database routes → Database controller: dispatches
backend/routes/databaseRoutes.js - Jira controller → Credential store: reads and saves
backend/controllers/jiraController.js - Jira controller → Atlassian client: creates
backend/controllers/jiraController.js - Jira controller → Issue fetcher: fetches issues
backend/controllers/jiraController.js - Jira controller → Page fetcher: fetches pages
backend/controllers/jiraController.js - Jira controller → Graph transformer: transforms issues
backend/controllers/jiraController.js - Jira controller → Graph queries and writes: saves graph
backend/controllers/jiraController.js - Database controller → Graph queries and writes: queries graph
backend/controllers/databaseController.js - Atlassian client → Atlassian APIs: sends requests
- Issue fetcher → Atlassian APIs: fetches issues
- Page fetcher → Atlassian APIs: fetches pages
- Credential store → PostgreSQL: persists credentials
- Graph queries and writes → Neo4j graph store: reads and writes
README.md