Integrations

Axoria supports native integration with GitHub for development workflow automation.

Access at Organization Settings → Integrations.

---

GitHub

The GitHub integration enables automatic branch creation when an issue is created.

When an issue is created in a project with the integration enabled, Axoria automatically creates a branch in the linked repository using the format:

axoria/{type}/{key}-{title-slug}

Example: axoria/bug/SHOP-42-cpf-validation-failure

---

Organization Setup

1. Go to Organization Settings → Integrations.
2. Click Add Integration → GitHub.
3. Enter a GitHub Personal Access Token (PAT).
   • The token needs the repo scope for private repositories or public_repo for public ones.
   • Credentials are stored encrypted.

Per-Project Setup

Each project can activate the integration independently:

1. Go to Project Settings → Integrations.
2. Enable the GitHub integration created at the organization level.
3. Configure:
   • Repository: owner/repo or full URL (e.g. https://github.com/my-org/my-repo)
   • Base branch: the source branch for new branches (default: main)
   • Trigger issue types: select which issue types (e.g. BUG, TASK, HOTFIX) trigger branch creation

---

Behavior

• The branch is created asynchronously after the issue creation transaction commits.
• Branch name format: axoria/{type}/{KEY}-{slug} (slug generated from the issue title, max 50 characters).
• If the token lacks permission (403) or is invalid (401), the error is logged on the server. The issue is still created successfully even if branch creation fails.

---

Permissions

Only the organization Owner or Admin can configure integrations at the organization level. Project-level activation can be done by members with the PROJECT_ADMIN role.

---

Available Integrations

GitHub

Link GitHub repositories to Axoria projects:

• Pull Requests: mentioning an issue key in a PR title or body (e.g., SHOP-42) automatically links the PR to the issue
• Commits: commits referencing an issue key in the message are listed in the issue detail panel
• CI Status: the latest CI check status of a linked PR is shown on the issue
• Auto-close: merging a PR can automatically move the linked issue to DONE status (configurable)

How to configure:

1. In Integrations, click Connect → GitHub.
2. Authorize Axoria on GitHub OAuth.
3. Select the repositories you want to link.
4. Configure auto-close rules (optional).

---

GitLab

Equivalent functionality to GitHub:

• Link Merge Requests to issues via key in title/description
• Commits referencing issue keys
• CI/CD pipeline status on the issue
• Auto-close on MR merge

---

Bitbucket

• Link Pull Requests to issues via key in the message
• Commits referencing issue keys

---

ServiceNow

Bidirectional incident synchronization:

• ServiceNow → Axoria: incidents created in ServiceNow can automatically generate Axoria issues with type BUG or HOTFIX
• Axoria → ServiceNow: moving a linked issue to DONE updates the corresponding ServiceNow incident
• Configurable field mapping (priority, category, assignee)

---

Corporate SSO (SAML / OIDC)

Federated authentication for organizations with a centralized identity provider:

Protocol	Use Cases
SAML 2.0	Active Directory, Okta, Azure AD, PingFederate
OpenID Connect (OIDC)	Google Workspace, Keycloak, Auth0, AWS Cognito

How to configure:

1. In Integrations, click Configure SSO.
2. Select the protocol.
3. Enter the identity provider (IdP) metadata:
   • SAML: metadata URL or XML upload
   • OIDC: issuer_url, client_id, client_secret
4. Configure attribute mapping (email, name, groups).
5. Activate and test with a pilot user.

With SSO active, organization members log in via the configured IdP. Local logins (email/password) can be disabled to enforce SSO usage.

---

Permissions

Only the organization Owner or Admin can configure integrations. Regular members do not have access to the Integration Hub.