title: Zoho BugTracker integration description: Bring Zoho BugTracker bugs into Sharkly with an access token: bind a portal, pick projects, preview and import, with incremental re-imports and rollback.
Zoho BugTracker integration
The Zoho BugTracker integration brings bugs from Zoho BugTracker (official SaaS at bugtracker.zoho.com) into Sharkly: bind a portal, preview and import by project, re-import incrementally later, and roll back an import when needed. Open it from Integrations under Zoho BugTracker.
Connect a portal
- Open Integrations and select Zoho BugTracker.
- Enter the Bearer token (a Zoho BugTracker access token) and the Portal ID.
- Confirm, and Sharkly validates the
bugtracker.zoho.comconnection with the token; a successful validation saves an organization-level connection.
After connecting, an identity summary shows the portal and how many projects it can read. Create the access token from Zoho BugTracker's official API documentation; the exact entry point follows Zoho's docs.
One Zoho BugTracker project under a connection imports into one Space only; to change the target Space, roll back the previous import in the import history first.
Credential health
The connection keeps showing a credential health status: when the token expires or Zoho rejects it, the status row states the reason and offers Update credentials — rotate the token in place instead of deleting and rebinding. An unknown status is shown as unknown.
Import
The integration page's Import walks four steps, with a progress strip at the top:
- Connection: confirm the saved credentials are usable;
- Scope: pick one of the projects the portal can read, plus the target Space;
- Preview: read and preview the tasks in that project to confirm the range;
- Confirm: start the import.
The import normalizes Zoho BugTracker bugs into Sharkly Tasks; assignees who cannot be matched to an Organization member are captured as external accounts with the same rules as a Jira import.
Incremental re-imports
Importing the same project again is incremental: tasks already imported are not duplicated, and only changed content is refreshed. Existing tasks are skipped by default; to refresh historical data, roll back the previous import in the import history and import again.
Import history
Each import is a job record. The import history on the integration page shows progress and failures, and lets you retry or roll back a completed import:
- a rollback deletes only the tasks that import created and that still belong to it;
- tasks created by earlier imports, and any local edits, are neither deleted nor reverted;
- if the import created nothing new (updates/skips only), a rollback deletes nothing.
Troubleshooting
Where do I find the Portal ID?
The Portal ID is the numeric identifier of your Zoho BugTracker portal, visible in the portal URL and Zoho's console. It is required on the bind page; the connection validation is the final check.
The token expired — what now?
Generate a new access token in Zoho, then use Update credentials on the status row of the Zoho BugTracker integration page to replace it. Completed imports are unaffected.
Does the import write back to Zoho?
No. The integration focuses on importing bugs into Sharkly and following up incrementally; there is no real-time two-way sync. Later Zoho-side changes are picked up by importing again.