Azure DevOps
Import supported projects, iterations, work items, pull requests, builds, releases, assignees, attachments, and board membership from selected links. Map the selected provider structure into the relevant Allocyn project and boards.
Integrations and API
Connect delivery systems without losing ownership.
Import delivery activity from GitHub, Azure DevOps, or Jira. Connect other workflows through the read-only API and signed webhooks.
Connect the systems where delivery work already happens.
Choose which projects or repositories to connect and where their supported records belong in Allocyn. Imports use the access you authorize and retain links to their source. Available record types differ by provider.
GitHub
Import supported repositories, issues, pull requests, commits, and assignees using customer-authorized access. Use the imported delivery activity in the Allocyn project chosen for that repository.
Jira
Import supported projects, issues, assignees, attachments, and mapped workflows into an Allocyn delivery structure. Choose how supported provider statuses correspond to the destination board.
Choose what is connected and how it is mapped.
Set project and board links, field and status mappings, and import schedules. You can disable a connection when it is no longer needed.
Imports are one-way into Allocyn. Update source records in GitHub, Azure DevOps, or Jira; Allocyn does not write changes back.
Use documented API access and webhooks for supported workflows.
Administrators can create API clients with limited permissions and request limits to read supported project, work-item, people, and generated-report metadata. Keep client credentials private.
Send selected Allocyn events to a configured service through signed webhooks. The receiving service can verify each signature.
Confirm the records and direction your workflow needs.
Check supported records and mappings before connecting a tool. Try an import during your trial, or contact us about the provider and record types your team needs.