Skip to main content

SIMS Ticket Hub — March 2026: Asana, Salesforce, Dynamics 365, Jira Org Sync, Personal PAT & Timesheet Notifications

March 10, 2026

by SIMS Tech5 min read
announcementticket-hubreleaseintegrationsasanasalesforcedynamics-365jiratimesheetai-assistantcompany-news

SIMS Ticket Hub — March 2026: New Integrations, Jira Org Sync, Personal PAT & Timesheet Notifications

We're pleased to announce a substantial update to SIMS Ticket Hub — new source platforms, organization-level Jira sync, personal tokens for the AI assistant, timesheet license notifications, and a refactored integrations layer for easier extension and maintenance.

🚀

What's New in This Release

Three new integrations (Asana, Salesforce, Dynamics 365), full Jira organization-level sync (org-fill), personal PAT tokens so the AI assistant acts on your behalf in ADO/Jira/GitHub, and timesheet license reminders (in-app + optional email) for paid users. Under the hood: a clean provider registry and SOLID refactor of the integrations module.

New Integrations: Asana, Salesforce, Dynamics 365

Ticket Hub now aggregates tickets from three additional platforms:

| Platform | What you get | |----------|----------------| | Asana | Connect your Asana workspace; aggregate tasks and projects into the same unified table with ADO, Jira, and GitHub. | | Salesforce | Pull cases, tasks, or custom objects into Ticket Hub for a single view alongside your dev and project tickets. | | Dynamics 365 | Connect via Azure AD (Tenant ID, Client ID, Client Secret). Work items from D365 join the dashboard; credentials are stored encrypted and never returned in API responses. |

All three use the same patterns you already know: add a site, provide credentials or OAuth, and sync. Filtering, grouping, timesheet, and AI assistant work across all connected sources.

🔷

Jira Organization-Level Sync (Org-Fill)

Organizations that use Jira Cloud can now run full, incremental, or backfill sync at the org level — same as for Azure DevOps. One click on the organization page pulls all configured Jira projects into the shared context. The AI assistant and timesheet then use this data for every member of the organization.

Personal PAT Tokens — AI Acts as You

Organization members can store personal access tokens for Azure DevOps, Jira, and GitHub in their settings. When the AI assistant needs to perform an action in a connected system (for example, add a comment or fetch details), it uses your token and acts on your behalf. No shared org token required for MCP-style actions; each user controls their own credentials. If a token is missing, the assistant shows a short hint and a link to settings instead of failing silently.

Timesheet License Notifications (Paid Tier)

For users with an active timesheet license:

  • First login after license grant — A one-time splash explains that full timesheet access is available for the license period; after expiry, only "yesterday" remains. Dismissing is remembered so it doesn’t show again.
  • Five days before expiry — An in-app notification in the tray reminds that the license is about to end. Optionally, super-admins can enable an email reminder (in addition to the in-app one) so users get a heads-up in their inbox. Language follows the user’s locale (e.g. EN/UK).

This helps paid users and admins avoid surprise loss of timesheet access.

Integrations Refactor — Cleaner Architecture

The integrations module has been refactored for clarity and extensibility:

  • Provider registry — New sources (e.g. Asana, Salesforce, D365) are registered in a single place; org-fill and other jobs route by site type without hard-coded branches.
  • No stub endpoints — All integration endpoints are implemented; no "coming soon" placeholders in production.
  • Timesheet and MCP — Timesheet data and MCP actions (e.g. add comment) are delegated to the correct provider via a clear interface, so adding a new platform only requires implementing that interface.

This makes it easier to add more platforms in the future and keeps the codebase maintainable.

RAG, Admin & Quality

  • RAG (AI assistant) — Embeddings continue to use full ticket description, comments with authors, and relationships; search remains scoped by organization and user access.
  • Admin — Super-admins keep full access to assistant analytics, session review, data stats (including Qdrant), and user management; org-admins see only their organization.
  • Tests & lint — Backend test suite (124+ tests) and lint are green; changes are verified as part of the release pipeline.

Summary Table

| Area | Before | Now | |------|--------|-----| | Source platforms | Azure DevOps, GitHub, Jira | + Asana, Salesforce, Dynamics 365 | | Jira sync | Per-site / per-project | Org-level full / incremental / backfill (same as ADO) | | AI assistant identity | Org or shared token | Personal PAT per user (ADO, Jira, GitHub) in settings | | Timesheet license | No reminder | Splash on first use; in-app + optional email 5 days before expiry | | Integrations code | Mixed branches | Provider registry, SOLID, no stubs |

Try It

For licensing, pricing, or a custom demo: vhlu@sims-service.com.


SIMS Ticket Hub — Unify your ticket management. One dashboard. Multiple platforms. Zero hassle.