How to Override Getint Behavior Using Custom Properties

Custom properties in Getint give you the ability to tweak and adjust how Getint operates by default to match your specific needs. By utilizing these properties, you can boost both the functionality and flexibility of your integrations, ensuring they match your business processes.

Use Cases for Custom Properties

1. Custom Workflows: Override default behavior to support specific workflows and automate processes based on custom criteria.

2. Enhanced Data Synchronization: Customize how data is synchronized between systems by adding rules and conditions that reflect your business needs.

3. Detailed Reporting: Capture additional data points for more comprehensive reporting and analytics.

How to Access Custom Properties

Jira Data Center

1. In the integration setup, go to Settings > Custom Properties.

2. Click on Add Property to define a new custom property.

3. Provide a name for the property and select the appropriate data type (e.g., text, number, date).

4. Specify any default values or conditions that need to be met for this property.

Getint On-Premise

1. In the integration setup, go to System > Custom Properties.

2. Click on Add Property to define a new custom property.

3. Provide a name for the property and select the appropriate data type (e.g., text, number, date).

4. Specify any default values or conditions that need to be met for this property.

Configure These Properties Using Available Flags

Use available flags to determine how these properties should influence the integration behavior. For example, you can set conditions to trigger specific actions or override default flags based on the custom property values.

Values That Can Be Modified

1. CLEAN_UP_MAX_RUNS

   • How many runs Getint cleans up in one cleanup cycle.

2. CLEAN_UP_INTERVAL_IN_HOURS

   • How long Getint waits between cleanup cycles.

3. CLEAN_UP_THREADS_COUNT

   • The number of cleanup threads working in parallel.

4. ENABLED_DETAILED_LOGGING

   • Getint prints more detailed information about errors.

5. MAX_NUMBER_OF_ITEMS_PER_RUN

   • The maximum number of items that Getint can sync per run.

6. MAXIMUM_AGE_OF_LOGS_IN_DAYS

   • Duration for which Getint will keep sync data.

7. FF_SKIP_COMMENTS_CREATED_BEFORE

   • Comments created before a specific date (e.g., 2024-01-01) will be skipped during syncs.

8. DO_NOT_STORE_BROKE_PIPELINE_SYNCS

   • If set to true, Getint won't save information about items that failed to sync. Useful for saving storage and when filters are applied.

9. MAX_HISTORY_CHANGES_PER_INTEGRATION_SUITE

   • Controls how many integration changes are stored in Getint (default: 20).

Specific Flags to Data Cleanup

1. CLEAN_UP_INTERVAL_IN_HOURS

   • Interval in hours for cleanup (default: 4).

2. NUMBER_OF_RUNS_TO_CLEAN_UP

   • The number of runs to clean per cleanup cycle (default: 500). Getint performs 10 cycles per cleanup, removing 5.000 runs of data per cleanup.

Save and Test the Configuration

1. Once you have configured the custom properties, save the settings.

2. Test your integration(s) to ensure that the custom properties are correctly influencing how Getint operates.

Support and Assistance

Our support team is available to provide guidance and assistance with configuring custom properties and overriding integration behaviors. For any questions or support needs, don’t hesitate to reach out to us here.