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 it in Prolaborate. After completing the configuration of the Jira integration on the Prolaborate side, the project may have been deleted in "Integrated Application Projects" on the Prolaborate side, or the "Custom Integrity Properties" may have been deleted in "Modelling Language" or the Project configured in the Prolaborate end pointed to the Jira project may be unreachable.
Possible Reason - 2
When configuring Prolaborate with JIRA Server, you have the option to choose the "JIRA Server V9 and Above" application setting.
Reference Document
Reference Ticket
Ticket ID: #4785
Subject: Jira Integration Issue for Prolaborate V4 with Jira V9
Department: Prolaborate Support
Ticket ID: #5815
Subject: Jira & Confluence communication
Department: Prolaborate Support
Q2. Issue with Jira Integration in Prolaborate - Application Credentials Invalid (or) Access Denied for this Project (Error)
Description
The customer reported that they are facing while adding Jira integration in Prolaborate. The error message states, "Application credentials are invalid, or access is denied for this Project".
Root cause
The Jira server is not configured with a firewall, leading to the occurrence of this issue.
Remediation
To address this issue, it is recommended to configure the Jira server with a firewall before attempting to connect the Jira Integration into Prolaborate. Ensuring the proper firewall settings will help resolve the problem and enable seamless integration.
Reference Document
How to integrate Enterprise Architect with Jira? (sparxsystems.com)
Reference Ticket
Ticket ID: #8290
Subject: Integration Prolaborate Jira
Department: Prolaborate Support
Q3. Installation and Configuration - Jira Server with Prolaborate
Jira server Installation
Please download the Jira server by using the below link.
Step by step instruction
Once you have downloaded the application, proceed to extract the files and choose the "Run as Administrator" option.
1. Click on Next Button.
2. Click on Ok button to access HTTP port.
3. Enter the HTTP Port and proceed by clicking the "Next" button.
4. Click on Install Button.
5. Once you have finished the process, proceed to click on the "Next" button. This will initiate the launching of the instance. Finally, click on the "Finish" button to complete the process.
JIRA Server Setup
1. Once you have launched the Jira server, choose the option "Set it up for me" and proceed to click on "Continue to “MyAtlassian".
2. On the landing page, please proceed to click on the "Generate license" option. Then, click on the "Yes" button to confirm and activate the generated license.
3. Enter your email address, username, and password, and proceed by clicking the "Next" button.
4. Once you have finished configuring the settings, proceed by clicking on the "Let's get started" button.
5. To proceed with the process, first, select your preferred language. Then, click on "Create a new project" and select a software option from the available choices.
6. Enter a project name and proceed by clicking the "Submit" button.
7. Jira server page will be open. From there, navigate to the newly created project and proceed to create an issue.
8. specify the issue type and enter a summary
Jira server Configuration on Prolaborate
1. Open the Repository menu and select “Integrated Application Project”.
2. Click on Add Project.
3. You can set a default name for it and Application as select the "JIRA Server V9 and Above" option. Additionally, provide your email (JIRA Server Username) and password (JIRA Server Password). Finally, click on the "Validate connection" button.
4. Upon validation, choose your Jira Project and save the selection by clicking the designated button.
5. Navigate to the Repository menu and choose the "Modeling language" option. From the landing page, select the custom property and click on "Add Property." Then, proceed to select "Add Integration Property."
6. On the landing page please add the name, Application as "Jira Server V9 and Above” and select Project. Also add the item type and click save button.
7. Launch the modeling language software and choose the "Archimate 3.1" option.
8. Access the Default Profile and choose the desired profiles.
9. Access the dropdown field for custom properties and select the newly created Integrated Jira project. Afterward, click on the save button.
10. After you have finished following the steps, open the repository and choose the desired element. Additionally, access the element's properties tab and select the option "Open Form Designer".
11. Drag and drop the project from the customer properties section, and then click on the save button.
12. Access the element properties tab to find the Jira server listed in the dropdown field. Click on the add symbol to choose the desired items and add them to the element.
Reference Document
Q4. Display Issues with Long Jira Names on Prolaborate Custom Property Page
Description
When utilizing long names in Jira for various entities such as tasks, epics, or user stories, the integration with Prolaborate's Custom Property page exhibits unexpected behavior. Instead of displaying the complete name of the entity, the display is truncated or improperly formatted, resulting in an inaccurate representation of the entity's name.
Possible Reason
This issue has been identified as bug in Prolaborate version 4.x. In this versions, there is a text overlap problem within the Jira integration module. Specifically, when the name of a Jira item is lengthy, it overlaps in the preview of the Jira configuration within Prolaborate.
Workaround
To address the overlap issue, it is recommended that customers upgrade to Prolaborate version 5.2, where this issue has been resolved. If customers encounter the overlap issue, we advise them to upgrade their Prolaborate version to 5.2 to rectify the issue.
Reference Ticket
Ticket ID: #4454
Subject: [Bug] Jira issue type custom property overlap
Department: Sparx Platform Support
Related Articles
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 ...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 ...Known Issues - Jama Integration
Pick List Items are missing in EA thick client Description Picklist values are missing in EA thick client. When accessing from EA, the system integration reads picklist information as an empty string. Picklist in Jama Picklist in Enterprise Architect ...Known Issue-Model Connection
Encountering an "XML incomplete error" when attempting to connect to the model in EA. Description: When attempting to connect to the model in EA, users encounter an error message stating "XML incomplete error." Any attempts to modify the repository ...Known Issue: Transfer File to DBMS
Error while transferring file from EA to DBMS Description The customer trying to load some data into their Database and They don’t know how to set up the server connection. First they migrated the eapx file (from Sparx EA 15.2) to a qea file which ...