Naxis Technologies Docs
Live demo

Product guide

Issues & support

Issue trackers, project tools and support desks — the largest catalog, from tickets and boards to help-desk queues.

This category covers the sources engineering and support teams live in — code forges (GitHub, GitLab, Bitbucket, Azure DevOps, Gitea / Forgejo) and the trackers that sit around them — issue trackers (Jira, Linear) and operational logs (Sentry, PagerDuty). Each becomes a document — an issue with its full comment thread, a merge request, an incident with its responders' notes — so “how did we fix this” and “have we seen this before” answer from the record itself, not from asking around.

Every connector here takes one API credential — a personal access token, an API key, or an email-plus-token pair — created in that provider's own settings, never a sign-in flow. Each is read-only: only reads are ever issued, and nothing is ever written back to the source. Most sync everything by default and let you narrow to specific repositories, projects or teams; all of them keep syncing on a schedule once set up.

A few of these mirror the provider's own visibility rather than relying only on this source's access groups — GitLab's confidential issues, Jira's per-project Browse permission, Linear's private teams and PagerDuty's team membership all narrow automatically where the provider exposes who can see what. The rest — GitHub, Bitbucket, Azure DevOps, Gitea/Forgejo, Sentry — rely entirely on the access groups chosen when the source is set up; the provider's own collaborator or permission list is not read for this.

The connectors

Was this page helpful?
Was this page helpful? Sign in with Google Sign in to tell us — or leave a comment.

Last updated 20 Sep 2026