Getint Jira Server / Jira Data Center App (Native)
Overview
Getint for Jira Server and Jira Data Center is installed directly in Jira as a native Atlassian application.
The application runs within your Jira environment and stores its configuration in the Jira database. Synchronization jobs are executed by Jira and do not require a separate Getint-managed service.
This deployment model is commonly used by organizations that require:
Local infrastructure control
Internal network connectivity
Data residency requirements
Restricted outbound access
Jira Data Center deployments
Self-managed environments
Installation from Atlassian Marketplace
Open Administration → Manage Apps.
Select Find new apps.
Search for the required Getint application.
Install the application.
Apply the license if required.
After installation, the Getint administration section becomes available in Jira.
Licensing
Getint licenses are managed through Atlassian Marketplace licensing.
To verify the current license:
Navigate to Administration → Manage Apps.
Locate the installed Getint application.
Review the license status.
If the license expires, synchronization jobs may stop running depending on the licensing model.
Configuration Storage
Getint stores integration configuration and synchronization metadata in the Jira database.
No separate database is required.
The application creates dedicated tables for:
Connections
Integrations
Synchronization records
Processing status
Execution history
Error tracking
System configuration
The exact table names may vary between application versions.
Scheduled Jobs
Getint uses Jira scheduled services to execute synchronization tasks.
These jobs are responsible for:
Running integrations
Processing synchronization queues
Cleaning up historical data
Updating synchronization status
Logs
Getint creates dedicated log files for troubleshooting and operational monitoring.
Log Location
The application stores logs in:
If the Jira environment does not contain a log directory, Getint creates:
Log Contents
Logs may contain:
Synchronization activity
API requests and responses
Processing statistics
Error details
Diagnostic information
Support may request log files during troubleshooting.
Data Retention
Synchronization activity generates database records and log entries over time.
Administrators can configure retention periods to control storage growth.
Logs are retained for 14 days by default. You can adjust the retention period to a shorter or longer duration based on your organization's requirements.
Cleanup Process
A background cleanup job periodically removes:
Historical synchronization records
Old execution logs
Expired processing data
Retention settings can be configured from the Getint administration section.
Performance Considerations
Synchronization performance depends on several factors:
Jira server resources
Database performance
Integration complexity
Number of synchronized records
API limitations of connected systems
For larger deployments, monitor:
CPU utilization
Memory consumption
Database growth
Synchronization duration
Testing
Before deploying integrations in production, validate the configuration in a testing environment.
Recommended validation activities include:
Connection testing
Authentication verification
Field mapping validation
Synchronization rule testing
Permission verification
Testing helps identify configuration issues before production use.
Upgrade Process
Application upgrades follow the standard Atlassian Marketplace process.
Before upgrading:
Review release notes.
Create a Jira backup.
Verify compatibility with your Jira version.
Test the upgrade in a non-production environment when possible.
Uninstallation
Removing the application stops all Getint synchronization jobs.
Administrators should review:
Existing integrations
Historical synchronization data
Log files
Database records
Depending on organizational requirements, additional cleanup may be performed after uninstallation.
For deployment planning, security reviews, or support questions, contact the Getint team.
Last updated
Was this helpful?