Correctly display the Orgs/Container's of a linked security tool when connecting them to Jira on the toolchain page

Issue Summary

Users can associate security containers from tools such as Synk, Lacework, etc with their Jira projects through the toolchain page. When selecting which container to associate with the project, containers which are already associated with the project should appear as disabled options.

Note that this issue is not specific to Snyk, Lacework or security, however, it was reported in that context.

This does not actually block users from associating more containers but creates confusion, as it appears their actions are not taking effect.

The reason for this bug is currently we fetch the first 20 containers a user can link + the first 100 containers a user has already linked, and then compare the responses to see which of the 20 containers are already associated. A simple approach of increasing the page size is not possible because downstream services enforce a maximum page size of 100.

Steps to Reproduce

• Connect to Jira to a security tool such as Synk, Lacework, etc
• Link >100 containers to a Jira project via Toolchain

Expected Results

If you have > 100 containers associated with your project, the already linked containers appear as disabled/locked options and are not allowed to be added again.

Actual Results

If you have > 100 containers associated with your project, you may see a UI bug whereby some containers which are already linked do not appear as disabled options. The user can subsequently attempt to associate these projects with their Jira project again, even though they are already associated.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available