Search

How to narrow down your search results using the facets:
  • Articles about using, installing, and administering Jama will be in the Knowledge Base community.
  • Content about releases, webinars or product news will be in the Release Notes and Announcements community.
  • User questions about using Jama or bug reports will be in the Support community.
The search engine uses common functionality.
  • Boolean operators: AND in between terms will return results containing both terms; OR will return results containing either term.
  • Stemming: if you search for "review" it will return results for reviewing and reviewed.
1 to 24 of 24
Sort by

Blog Entry
Important change for Jira Cloud Authentication: Switch to API Token

Upcoming Atlassian change What this means for you: Failure to review or take action may cause a preventable break in communication between Jama and Jira Cloud Details Most Jira Cloud users are aware that Atlassian announced the December 1st (12/01/2018) deprecation of two forms of API authentication. The official announcement was made on March 1st. These changes do not impact Self...

Jason's profile image

Discussion Thread 1
Broken Legacy Jira Connector

Ken's profile image

Discussion Thread 6
LDAP migration

Mark's profile image

Discussion Thread 5
Import from DOORS to Jama

Teertha's profile image

Discussion Thread 2
Converting filters to lucene search

Doug's profile image

Discussion Thread 1
Azure Container Instance and Azure Storage = permission issue

elena's profile image


Discussion Thread 3
Jira connectioon in Jama issue

James's profile image

Blog Entry
Atlassian Account changes may affect Jama/JIRA integration

Atlassian has made some changes to account verification with JIRA that may cause a sync with Jama to stop. This will affect some users of the JIRA Cloud, but not those who host their own JIRA instance. Users will need to go through Atlassian’s account change and verification process with the user setup for the integration if they appear to be affected. This can be done via https://id...

Steve's profile image

Blog Entry
Rally Connector FAQ

Rally Connector FAQ (Questions expand on click) Expand All Collapse All I can’t see the Rally Connector. Q: I don't see the Rally Connector in the Admin view. A: The Rally Connector requires an additional license to be activated. Please contact sales@jamasoftware.com to request a trial or to purchase. Why aren’t items syncing from Jama Software to Rally? ...

Abby's profile image

Discussion Thread 3
JAMA /REST API Permission

Joydeep's profile image

Blog Entry
How to troubleshoot Legacy Connector issues

Most of the legacy connectors allow you to set an email notification for when a sync is unsuccessful, as described in JIRA, Rally and TFS sections of the help guide . You can troubleshoot synchronization failures by tracking integration records in your project’s Activity Stream. You will need to configure your Activity Stream View for this, which can be done by opening the Activity...

Carmen's profile image

Blog Entry
New issue discovered with JIRA legacy connector in 2015.3 and hosted environment

We have discovered a new issue with the legacy JIRA connector in our latest on-premises and hosted releases. This issue occurs in only specific circumstances and is separate from the issue (SOS-BUG-1001) fixed in 2015.3 and hosted 2015/12/17. The JIRA sync will fail for all projects if both of the following conditions are met: Any project contains multiple item type mappings which sync ...

Kristina's profile image

Discussion Thread 11
PlantUML support

Sudha's profile image

Blog Entry
How to Video: Enterprise Architect (EA) Connector

#integrations

Jama's profile image

Blog Entry
JIRA Connector FAQ

Mapping How do you map a Release in Jama to JIRA? Release type fields (standard and custom) can be synced from Jama to JIRA. The Release field must be mapped to a Version Picker field in JIRA. All valid versions in Jama must be added as versions in JIRA. Do I have to map all required fields in JIRA? If you have an issue in JIRA with a required field, you must map the required field...

Jama's profile image

Blog Entry
Table of permissions required for JIRA Connector

Jama versions 2014.1 and onward use REST API for the JIRA Connector. The table below has a detailed list of permissions that are required for the JIRA Connector to work properly. By default, if the JIRA user is a member of JIRA-administrator, JIRA-users and JIRA-developers, it should have the below permissions. Project Permissions: Issue Permissions: Create Attachments is now r...

Jama's profile image

Blog Entry
JIRA Error org xml sax SAXParseException Premature end of file

**Applies to Jama 4.27 and Below** This error is caused by having ASCII control characters in the return xml from a JIRA SOAP connection. The error should point out the xml line number and the characters having an issue. If you get this error please contact support and submit the contour-integrationsync.log from the time in which the sync was attempted. This will be located in tomcat/logs...

Jama's profile image

Blog Entry
My JIRA is behind a firewall or on a VPN, but you host my instance of Jama. How can I connect them?

In order to connect to Jama hosted, your JIRA instance must be available to our IP publicly. You can resolve this by adding our IP to pass through your firewall or VPN. To find the IP of your Jama hosted instance, follow these steps: 1. Open a command prompt 2. Ping your instance: ping abc.jamasoftware.com (Originally posted by Matt Mickle) #integrations

Jama's profile image

Blog Entry
How to update Jama when JIRA URL changes

If the JIRA URL has changed from the one that you originally set in you JIRA connector, either because you changed your JIRA server or changed JIRA configurations, you need to update the JIRA URL in Jama in order for the sync to continue to work.The JIRA URL in the JIRA Connector configuration page as well as the JIRA URL in all the items that are synced to an issue in JIRA need to be updated....

Jama's profile image

Blog Entry
Troubleshooting Common Integration Issues

Jama cannot make a successful connection to my HTTPS-enabled server If you have SSL/HTTPS enabled on your Integration server and your Test Connection result is reporting an SSL Handshake exception, you may need to add the server's SSL certificate to the list of trusted authorities in your Jama server's underlying Java installation. This will enable Jama to make a proper connection with JIRA's...

Jama's profile image

Blog Entry
JIRA throws "Unexpected error" in integration-sync logs

Determining the cause On the contour-jirasync.log file, "Unexpected Error" can come up for a number of reasons. It will look like this error: [ERROR] - FAILING ITEM SYNC [item PROJ-1] : Unexpected error The first step to troubleshooting this issue is turning on the DEBUG level for logging. To do this, login as the "root" user in Contour. Go to the Logging tab. Edit the levels from...

Jama's profile image

Blog Entry
How to sync a release field over to Jira and Rally

1) Jira: Release type fields (standard and custom) can be synced from Jama to Jira. They MUST be mapped to a "Version Picklist" field in Jira. All valid versions in Jama must be added as versions in Jira. You can't map to a string or a standard drop down. This will simply send over the integer of the version. 2) Rally : Release type fields (standard and custom) can be synced from...

Jama's profile image

Blog Entry
Rally Connector connection

Some of our customers have been having issues with connecting to the Rally servers through Contour's Rally Connector. Here are a few tips: You need to use / slm in the URL. You can see this on the login screen for any Rally server. For trials connect to: https://trial.rallydev.com/slm For any other accounts connect to: https://rally1.rallydev.com/slm If this does not work please...

Jama's profile image