TFS4JIRA Self-Hosted | Allowing users to see only specific synchronization profiles
Problem
TFS4JIRA does not support internal permissions for synchronization profiles.
Solution
A viable workaround is to run multiple synchronizers against the same Jira and ADO instances. This can allow you to make separate teams to work on different projects without risking accidentally changing another team’s profiles.
Run multiple synchronizers. You may opt to use virtual machines for this, as this will allow you to have different system users and passwords.
You can connect all synchronizers to the same two instances.
You choose to use the same user credentials or different ones for each synchronizer running.
It is recommended to not use the same projects in two or more synchronizers, as you run the risk of creating duplicates and having all synchronizers fail to work properly.
This solution only requires a single license, even if you host multiple instances of the synchronizer. The license for the app is checked from your Jira instance.