Integration Creation
Creating your integrations
Ready for the fun part? It is time to create your integrations! For detailed step by step instructions on how to create the integrations by Git service, please refer to our Integration guides Integration Guides.
All of the planning and decision making from the previous steps get put to work during the integration creation process. You should now have confidence choosing which repositories to include, and which Project Association permissions to apply to limit visibility. We suggest that you disable any features that you will not be using before creating your integrations as discussed previously.
If using multiple integrations, consider creating only one or two integrations at a time. Additionally, please wait until the initial indexing phase completes for the new integration before going through the process of creating the next one. This reduces the probability of rate limiting issues or overloading the application with a large backlog of tasks.
While this suggested approach may take a bit longer to complete, it avoids common issues or quickly raises important issues to address before committing the time to create all of your integrations. For any such issues, contact our support team to work through the problem and save time.
Post Integration creation configuration
Now that you have created all of your integrations, we recommend the following actions to round out your configuration.
Edit Integration feature settings
Display name
We suggest editing each of your integrations and modifying the display name to better reflect what is included, or what org/group is connected. Please see Edit Integration connection settings for details.
Require user PAT
We strongly recommend enabling the “require user PAT” integration setting. This option will require all of your users to provide their own PAT the first time they go to create a branch or pull/merge request from inside Jira.
This is important, as we will then use their PAT to authenticate newly created branches and pull/merge requests and attribute them to the correct user on your Git Service. If this option is not enabled, the branch/pull/merge request will still be created, but it will be authenticated using the integration connection credentials, and will be attributed to whatever account the credentials are associated with. Please see Require Personal Access Tokens for further details.
Enforce Git Service Permission
We strongly recommend that you enable the ‘Enforce Git service permissions” option if you are using the ‘Require User Pat’ option. This setting will pull the repo permission for each user that provides their PAT, and will only show them Git data that they have permission to. Please see Enforce Git Service Permissions for details.
Tuning the Reindexing interval
Once your integrations are all been configured, and they have indexed successfully for a day or two, we suggest that you go in and tune your reindex interval. To do this, you will need to use the Indexing queue viewer to see how long your indexing is taking. Once you know your previous indexing duration, set the reindex interval to a few minutes more than the duration value. Please Recommended reindex Interval for details.
