Feature comparison: Cloud Native VS Self Hosted
Last updated onOct 31, 2025.
1. High-level Overview
Hosting and Deployment | Cloud Native | Self-hosted |
No installation required | ||
No additional costs of hosting and deployment | ||
Automatic updates and maintenance | ||
Features | Cloud Native | Self-hosted |
Built-in fields synchronization | ||
Attachment synchronization | ||
States and Statuses synchronization | ||
User Mapping | ||
Comment synchronization | ||
Initial synchronization | ||
Synchronization filters | ||
Issue Hierarchy support | ||
Issue Linking | ||
Profile migration | PLANNED | |
Check-ins support |
2. Built-in Fields Support
Fields | Cloud Native | Self-hosted |
Title / Summary | ||
Description | ||
Assignee | ||
Reporter | ||
Components / Area | ||
Sprint / Iteration | ||
Story Points | ||
Priority / Severity | ||
Fix Version / Affected Version | ||
Release |
3. Field Types Support
Field Types | Cloud Native | Self-hosted |
Custom fields based on built-in fields | ||
Custom fields created by add-ons | ||
Labels | ||
Text - single Line | ||
Text - multi line (plain text and HTML/Wiki) | ||
Number Field | ||
Link / URL | ||
Single choice fields | ||
Multiple choice fields | ||
Date Pickers | ||
Date and time pickers | ||
User Picker | ||
Group Picker | ||
Time tracking fields | ||
Azure DevOps test steps synchronization |
4. Feature details
Feature | Cloud Native Synchronizer | Self Hosted Synchronizer |
|---|---|---|
Extra types of initial synchronization | ||
Multi-step transitions in status synchronization | ||
Active Directory Support | ||
User mapping by email | ||
Comment edits and deletion synchronization | ||
Automatic Sprint creation | ||
Jira Components* - used to group and organize issues in a project | ||
Sync ADO comment as internal content | ||
Map JSM customers to ADO users |
*Currently, there are no plans to include Components support.