External Integrations
Does Prolaborate V5 Support DevOps Integrations?
Yes, Prolaborate V5 enhanced to provide support for DevOps integration.
Cannot be able to attempt Login V5 and access other pages using Iframe URL.
The embedded URL (iframe share URL) is only applicable to the shared element page. Therefore, Login and other application page navigation will not work on the iframe.
Can SharePoint be embedded within Prolaborate?
No, SharePoint does not permit embedding information into external applications.
Can Jira items be added to a diagram in Prolaborate using Integration properties?
No, Jira items cannot be added directly to Prolaborate diagram properties using Integration Properties. This limitation exists because Enterprise Architect does not support tagged values for diagrams.
Jira items can only be linked to individual model elements (such as classes, components, etc.) through the Integration Property in Prolaborate. Unfortunately, this functionality does not apply to diagrams.
Unable to add Jira project in Prolaborate
An error message stating “Application credentials are invalid (or) access is denied for this Project” appears when adding Jira integration (Server) in Prolaborate. This issue may occur if the Jira server is not properly configured with the required firewall settings.
To solve this issue, ensure that the Jira server is configured with the appropriate firewall settings before connecting Jira integration to Prolaborate. This will allow the integration to proceed without issues.
For more details, on how to add a Jira project, click here .
Why does the “Not Able to Connect with Jira!” error appear in Prolaborate?

This error occurs when Prolaborate cannot connect to Jira due to issues such as Jira being inaccessible, the linked Jira project being deleted or removed, incorrect or outdated connection details, network connectivity problems, or an incorrect Jira Server version selection in Prolaborate. Ensuring Jira is accessible, verifying the project configuration, updating connection details, checking network settings, and selecting the correct Jira Server version can help resolve the issue.