Comparison of the DC version versus Cloud version of the Kepler - SQL Query Fields plugin

The Cloud version of our plugin offers unparalleled accessibility and ease of deployment. Customers can quickly leverage the plugin's features without requiring dedicated server infrastructure.

Additionally, updates are automatically managed by Atlassian's Cloud platform, ensuring access to the latest features and security patches.

However, customization may be limited due to restrictions imposed by the Cloud platform, and customers rely on Atlassian for availability and regulatory compliance.

On the other hand, the Server/Datacenter version provides full control over the infrastructure, allowing advanced customization and tailored management of data security and privacy.

Customers also have the option to manage their scalability and precisely address their unique business requirements.

In essence, the Cloud version has enabled us to automate certain features present in previous "Server/Datacenter" versions, thanks to the advantages of Cloud architecture where computing power and performance are higher.

For example, in the case of an autocomplete field, we are not required to specify from which letter the search begins.

The search starts from the first letter, and we do not have to worry about processing speed or computing power.

Here is a comparative table of the features of our plugin for the Jira Cloud platform compared to Jira Server/Datacenter.

Versions	DC/SERVER	CLOUD
Security	Security measures include encryption of client data, ensuring that sensitive information remains confidential and protected against unauthorized access. It's the responsibility of the client to manage the security of their instance.	Cloud version utilizes advanced security measures to protect client data. Employing modern encryption techniques, we ensure that your information remains secure and confidential. Atlassian takes charge of instance security, ensuring that security measures are always up-to-date.
Installation	Direct installation from the Atlassian Marketplace.	Direct installation from the Atlassian Marketplace.
Installation	Installation with JAR file.	Installation via the Atlassian-connect.json link.
Licence	Purchase the license from the Atlassian Marketplace (Monthly or annually).	Purchase the license from the Atlassian Marketplace (Monthly or annually).
Licence	Possibility of having a promotional code.	Possibility of having a promotional code.
Maintenance	Involvement of a Jira Administrator for plugin update.	Transparent.
Configuration	Access: Manage Apps > SQL CUSTOMFIELD ADMINISTRATION (on the left menu)	Access: Apps > SQL CUSTOMFIELD CLOUD (in the dropdown menu).
	Custom fields are displayed on creation screens by configuring the screens in the screen settings.	No possibility to add the custom field on the creation screens.
	Adding data sources on the plugin administration page. Adding a custom field in Issue types, and configuration after its creation.	Creating, testing, and managing data sources and custom fields on the same page. It makes plugin administration very easy and quick.
	The plugin's custom fields are mixed with custom fields of other types.	All plugin's custom fields are found in the same interface.
	JQL filters support SQL custom fields, enabling precise issue filtering based on SQL field values.	JQL filters don't support SQL custom fields
Options	Creating custom fields with complex queries.	Creating custom fields with complex queries.
	Possibility to add the custom fields to a single project, all projects, or to a particular issue type.	You can add the custom field to a project/issue type by specifying the project/issue type key for authorization.
	Testing custom field configurations.	Testing custom field configurations.
	Support for 6 types of custom fields (Static field, Autocomplete, Simple/Multiple Select, Radio, Checkbox, Table).	Support for 5 types of custom fields (Autocomplete, Simple/Multiple Select, Radio, Checkbox, Table).
	Ability to use Dependent Fields and dynamic parameters in SQL queries	Ability to use Dependent Fields and dynamic parameters in SQL queries.
	For a Table type field, it is possible to modify, add, or delete rows. Searching and displaying with pagination are possible. Exporting the table to an Excel file is possible.	For a Table type field, you can modify, add, or delete rows. Searching and displaying with pagination are possible. Exporting the table to a PDF, Excel, CSV file, or simply copying the table to the clipboard is possible.
	Recording data for a plugin field is done either by assigning a value in the creation screen or by the default value in the configuration.	Recording data for a plugin field is done either in the Issue window, where you must select or enter a value, then click the Save button to save the value for the custom field, but only for the ticket on which it was saved.
	For Autocomplete type fields, data loading can be manual or automatic. Searching by exact word or letter. Configuration of how many letters to start the search from. Limiting the number of returned results.	For Autocomplete type fields, data loading is automatic. Searching by a word can be: starts with, contains, ends with, or exact value. There is no configuration; the search starts as soon as the first letter is entered.
	Linked the jira fields together.	Can only link SQL custom fields together.
	Ability to use dynamic parameters for your SQL queries.	Can't use dynamic parameters for your SQL queries.
REST-API	Interaction with the Kepler plugin using Rest API calls.	Not possible.