Comparison of the DC version versus Cloud version of the Kepler - Merging Documents Plugin

The Cloud version of our plugin provides exceptional accessibility and effortless deployment. Users can swiftly utilize the plugin's capabilities without the need for dedicated server infrastructure.

Moreover, updates are seamlessly handled by Atlassian's Cloud platform, guaranteeing access to the most recent features and security patches.

Nevertheless, customization options may be constrained by restrictions imposed by the Cloud platform, and users depend on Atlassian for availability and compliance with regulations.

Additionally, the Server/Datacenter version provides users with extensive control over infrastructure, enabling advanced customization and personalized management of data security and privacy.

Furthermore, customers retain the flexibility to oversee scalability and precisely address their individual business requirements.

In essence, the Cloud version has empowered us to automate certain features found in previous "Server/Datacenter" versions, leveraging the advantages of Cloud architecture, which offers superior computing power and performance.

We have prepared a comprehensive comparison table of the features of our plugin for the Jira Cloud platform and Jira Server/Datacenter. This table highlights the differences and similarities in functionality, performance, and compatibility between the two versions of our plugin.

Versions	DC/SERVER	Cloud

Versions	DC/SERVER	Cloud
Security	Security measures include encryption of client data, ensuring that sensitive information remains confidential and protected against unauthorized access. Clients manage their own instance security.	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.
Storage	In the Data Center/Server version, file storage is managed locally on the user’s machine. This setup is typically suitable for organizations that prefer to maintain control over their data and have the necessary infrastructure to support local storage.	The Cloud version does not store files locally but stores them in Jira. When users merge documents, the merged file is automatically attached to the attachment field of Jira.
Installation	Direct installation from the Atlassian Marketplace.	Direct installation from the Atlassian Marketplace.
Installation	Installation with JAR file.	Installation via the descriptor atlassian-connect.json url.
License	Purchase the license from the Atlassian Marketplace (Monthly or annually).	Purchase the license from the Atlassian Marketplace (Monthly or annually).
License	Possibility of having a promotional code.	Possibility of having a promotional code.
Maintenance	Involvement of a Jira Administrator for plugin update.	Transparent update process managed by Atlassian.
Configuration	Not available	Will be added soon
Usage	After plugin installation, a panel displays on the right side in Jira view issue. This panel shows all MS Office and PDF files attached in the Jira attachment field in a table where each line represents a file. We have the option for ordering files with arrows (up, top up, down, to bottom). The panel have two buttons one for refreshing page the second is the merge button. The panel has two buttons: one for refreshing the page and the second for merging the documents.	After plugin installation, a panel displays on the right side in Jira view issue. This panel shows all MSOffice and PDF files attached in the Jira attachment field in a table where each line represents a file. We have the option for ordering files with arrows (up, top up, down to bottom). We also have the option of sorting files alphabetically, by size, and by creation date, which is not available in DC/Server. The panel has two buttons: one for refreshing the page and the second for merging the documents.
REST-API	Interaction with the Kepler plugin using Rest API calls.	Kepler merging documents uses Jira Rest Api to get Jira attachment field files to merge them then post them to the Jira attachment field using OAuth.
Download files	Users can download all their files.	Users can download all their files.

In summary, the Cloud version of the Kepler - Merging Documents plugin provides a more accessible and scalable solution, leveraging Atlassian's Cloud platform's advanced features.

The Server/Datacenter version offers greater control and customization capabilities, suitable for organizations with specific infrastructure and security requirements.

Both versions aim to enhance the document merging process in Jira, with ongoing updates to improve functionality and user experience.