Jira Align and Jira Integration: JQL Searches for Jira Issue ["changelog"] leads to Gateway Timeouts

Issue: Jira Align and Jira Integration: JQL Searches for Jira Issue ["changelog"] leads to Gateway Timeouts due to the large amount of data returned within the change log. This is especially an issue in cases where there are a large number of older issues being queried at one time. A common occurrence of this issue is when utilizing custom JQLs to integrate historic data from Jira to Jira Align.

Steps to Reproduce:
1. Map an older Jira Project with a large amount of data to a Jira Align Program
2. Run a custom JQL query under Jira Align Admin > Jira Settings > Jira Integration to bring in all the issues from the integrated Jira Project

Expected Results:
Jira Align is able to query the Data utilizing the custom JQL and the issues from the Jira Project create corresponding work items in Jira Align. The Jira Align and Jira Integration would utilize a new technique outside of the "changelog" to pull in audit information from Jira.

Actual Results:
The custom JQL API Call takes more than 30 seconds to respond to Jira Align leading to a gateway timeout and no work items created in Jira Align.

Workaround:
Modify the custom JQL query to bring in smaller batches of data from Jira in order to avoid the timeout. A potential technique would be to add a comment to 100 Jira Issues from the Project at a time using bulk edit in order for the connector to bring the issues in the scope of its routine pull of issues from Jira.