FAQs - JIRA
Q1. Links generated from Jira Items are exposing the entire repository when accessed
Answer
This behaviour is intentional, as Jira provides only essential information, and users typically access Prolaborate to access comprehensive data. If you wish to establish authentication before users access Prolaborate directly, you can achieve this by disabling the open community access (OCA) in the repository settings. This action will reroute the links to the Prolaborate login page.
Reference Ticket
Ticket ID: #6084
Subject: [Bug] - Enterprise Architect Jira Integration
Department: Prolaborate Support
Q2. How to resolve the error "Application credentials are invalid or access denied for this Project" in Prolaborate when adding a Jira project
Description
Customer tried to add a Jira project in Prolaborate, but received the error "Application credentials are invalid or access denied for this Project". The customer has tried using the same credentials as the dev environment, which worked, and has also tried using two different tokens.
Answer
1. Log in to your Atlassian account and click on "Administration" (refer to the screenshot below).
2. If you have multiple administrators, choose the admin user who handles Jira.
3. After selecting the admin, click on "Directory" and choose the user with the email address alex.vorderbruggen@medtronic.com (refer to the screenshot below for reference).
4. Once you've selected the user, click on the "Grant access" option.
5. Grant access for Jira Software (refer to the screenshot below).
6. Once these steps are completed, you should be able to add the Jira project in Prolaborate.
Note: Once you've granted the permission, kindly regenerate the token for the user and use it.
Reference Ticket
Ticket ID: #6146
Subject: Links from Jira to Prolaborate Disappear
Department: Prolaborate Support
Q3. Jira Items are not able to connect with Prolaborate elements?
Answer
When configuring Prolaborate with JIRA Server, you have the option to choose the "JIRA Server V9 and Above" application setting.
Reference
Ticket ID: #4785
Subject: Jira Integration Issue for Prolaborate V4 with Jira V9
Department: Prolaborate Support
Ticket ID: #6166
Subject: JIRA Filters
Department: Prolaborate Support
Related Articles
Known Issue - JIRA
Q1. "Not able to connect with Jira!" Error in Prolaborate Description Jira Items are not able to connect with Prolaborate elements and getting the below error. Possible Reason -1 The project may have been deleted on the Jira side after you configured ...Known Issue - Confluence
Q1. Failed connection in Confluence and Jira Integration Description Customer reported that they are unable to establish connection in both Confluence and Jira with Prolaborate. Customer shared the below screenshots of the configurations, Resolution ...FAQs - Microsoft Teams Integration
Q1. We are not able to confirm if any data is collected while using MS Teams Plug-in for Proloborate. If so, what data do you collect? Answer The data stored from MS Teams do not contain Personally Identifiable Information (PII), However, MS Teams ...Known issue: Access denied error when clicking SSO in Prolaborate(Autoscaling environment)
"Access denied" error when clicking SSO in Prolaborate. Description: The customer reported being unable to access Prolaborate. When clicking the SSO, they encountered an "access denied" error in Prolaborate. Possible Reason: As confirmed by the Dev ...FAQs - Prolaborate Installation
Q1:Can you suggest how we may configure Prolaborate using https and port 443. Do you have any links to documentation? Answer You can configure the Protocol and Port settings from Prolaborate Management typically located in C:\Program ...