How to enhance your experience with Exalate for Jira on-premise.
In this section
- How to sync issues automatically using Exalate API in Jira On-premise
- Jira On-premise: Subscribing a Script Runner listener to an Exalated event
- Ensuring Exalate does not synchronize when staging a production environment into test
- How to choose a destination project based on the parent option of a cascading select custom field
- Converting remote status changes to local comments in Exalate for Jira on-premise
- Exalate for Jira on-premise: Populating a required remote field from a specific field on your instance
- Setting the current authenticated user as a target issue reporter in Exalate for Jira on-premise
- Exalate for Jira on-premise: Setting a project based on the source issue custom field value
- Syncing a comment with a remote issue key in Exalate for Jira on-premise
- Syncing an assignee to a text custom field in Exalate for Jira on-premise
- Exalate for Jira on-premise: Syncing issue links to a custom field with Jira Issue Link API
- Exalate for Jira on-premise: Triggering issue transition based on the value of the remote status
- Testing Exalate in a Jira on-premise staging environment
- Updating a local custom field with a remote issue key in Exalate for Jira on-premise
- How to sync Table Grid Editor data
- JIRA Events the jiranode emits
- JQL Functions
- Jira on-premise: Sync between Select List (single choice) and text custom field
- Jira on-premise: Sync between Select List (single choice) and user picker custom field
- Jira on-premise: Sync between the Select List(single choice) custom field and issue type
- Jira on-premise: Sync Elements Connect custom field's value when they are connected to the same database
- Jira on-premise: Sync Select List (single choice) to a comment field
- Exalate for Jira on-premise: How to transfer sync settings when moving from one instance to another
- Set up how often Exalate will send emails
- Known issue: permission warnings in Exalate logs
