Standard channel (on-premises) Release Notes

By Kristina posted 04-27-2016 00:14

  

Jama Software 8.25 Standard

Release Date: 2018/05/15

Introducing Jama Analyze

Build on product development data your teams are generating from other tools — like Jama Connect, Jira Software, and GitHub — to get a far-reaching view into performance across teams. Learn more.

NEW CAPABILITIES

Verification and Validation

Now, your organization can more easily create, view and review test data. Here are the changes:

  • Test runs in Trace View:  Quality Engineers and Product Development leaders can now see your test data in the larger context of verification and validation. 

 Testrunsintraceview.png

  • Test data in reviews: Now both your test plan approach and your results can be reviewed and signed as part of your quality process. Simply select Send for review from the test plan or test cycle menus. You can also send a single test run for review.

testdatainreview.png

  • Test runner license: This new tailor-made license gives testers all the permissions they need to create test plans, execute tests, and manage defects. 
  • Restore test run order: This new button restores the original order after sorting with columns. For older data, a project reindex may be required to properly restore the order.

 

Rich text editor enhancements

  • CKeditor upgrade to version 4.9

  • Copy/paste and image support

      • Paste text and images from MS Office (Word or Excel) and most formatting is maintained. (Note: This does not apply when using Safari.)

      • Images are pasted inline, and automatically added to the item as attachments.
      • Toolbar copy/paste buttons are now replaced with keyboard options. When pasting, a bubble notification will appear with keyboard options.

  • Table support

      • Now you can select, copy and paste cells (rather than the content) more like Excel.

               tablesupport1.gif

      • For editing, the pencil icon has been replaced with the more familiar in-context right-click trigger.

        tablesupport2.png

      • Easily add a blank line above or below a table. When a table is directly against the edge of a rich text field, blue highlights guide you to select a button and add a line. No more hunting for the edge of a table!

               tablesupport3.gif

Improved User Guide

  • Help documentation has been deep cleaned and reorganized with users in mind.
  • Features include an improved glossary, "quick find" topics and sections for project, organization and system administrators.
  • A new content management system allows for more efficient updates, better search display and more clear and accurate content.

 

REST API

These updates can be found in the REST API Lab.

  • The newly added "labs" version introduces new endpoints and receives feedback without breaking or confusing supported versions. This version will not be officially supported and endpoints may change or be removed in future releases. The first endpoints to be released are administration related, please check the developer site for more details.
  • testruns - PUT and PATCH updates. These are located in labs as the changes are considered breaking for the existing v1 versions. The intent is to have the updates align with the item type field configuration and not mimic the Test Execution UI. Custom field updates are included.
  • activities - New event types to provide more refined detail.  BATCH_CREATE, BATCH_UPDATE,   BATCH_DELETE,  COPY,  BATCH_COPY, MOVE

 

Projects Reading View

Users are now able to toggle some item fields to show them in the Reading View.

  • Text fields (rich and plain), Pick lists, Releases, Date, Integer, Multi-select, Calculated fields, User fields, Userby fields, Rollup, Item type, Flag, URL and test-related fields such as Test Case Status.
  • There is an Admin configuration setting for the projects Reading View. Name and Description remain defaults, but admins can now configure settings for other fields to display the first time a user navigates to the Reading View.
  • When users toggle new fields in the Reading View, these selections persist.
  • There are slight changes to headings, font sizes, and hierarchy numbering.
  • Select the name and hierarchy numbering of a particular item to open Single Item View.

Select the Reading View button in the toolbar for these new benefits:

  • Export hierarchy from an advanced filter.
    • See hierarchy containers with the same styling as other items, but with a disabled checkbox.
    • Select and display fields with the gear icon.
  • See item icons next to the item ID.
  • Identify an empty description field with helper text: No information entered.
  • Reading View in both Projects and Reviews now share a similar look and feel.

 

Reviews

Speed up reviews by focusing on exactly what changed to arrive at the latest version.

  • Use the new Compare View to see changes inline, comparing current content to any past revision.

CompareView.png

  • Based on user feedback, the filtering side panel is now easier to use and more consistent with List View.

End of life

  • Unsupported v0 version of REST is no longer available.
  • SOAP no longer available.
  • Jama connectors for Rally and TFS are no longer supported. This is not to be confused with Tasktop (JIH or TIH) as these were separately licensed products managed within Jama.

 

RESOLVED ISSUES

SOS-DEF-219/MAIN-BUG-360/SOS-BUG-209: Adding widgets to some item types will throw error "Item Type Key XX is already being used by Item Type: YY."

SOS-DEF-993: New user on-boarding flow does not provide password strength hints, so users get stuck trying to enter Jama for the first time.

SOS-DEF-1241: Newly created diagram does not display in Internet Explorer 11; shows broken image symbol.

SOS-DEF-1362: Save New Item or Add Related shows a ghost modal that shows up after a user selects Save.

SOS-DEF-1503: Email notifications with HTML and inline images may fail due to server certificate issues.

SOS-DEF-1552: Insert New button in List and Reading View is not enabled.

SOS-DEF-1651: Line breaks cause unwanted updates during round-trip import.

SOS-DEF-1666: When exporting test runs that contain rich text test steps, HTML is visible in the report.

SOS-DEF-1732: In reviews, highlight appears on only first line of text if rich text field contains line breaks.

SOS-DEF-1756: Batch delete causes documentnode and document records to be out of sync.

SOS-DEF-1765: Long text is truncated in List View when inline editing (Chrome only).

SOS-DEF-1814: Rows do not line up in Trace View.

SOS-DEF-1853: There is no option in Test Run view to re-sort according to Test Group order.

SOS-DEF-1901: Test case status does not display in related item pop-up.

SOS-DEF-1942: In reviews, if " " is found in the HTML source of selected text, highlights don't work.

SOS-DEF-2038: Images float in Velocity HTML reports (they show up in wrong location in Word export).

SOS-DEF-2093: Clearing the value of pre-defined date fields will set the date to 12/31/1969.

SOS-DEF-2137: Rich text in test steps field does not honor HTML cleaner setting.

SOS-DEF-2169: Update Moderator button is not visible in the reviews List View.

SOS-DEF-2279: In reviews, highlighted text comment dialogue box appears off-screen when viewing full-page item.

SOS-DEF-2304: If using Internet Explorer 11, loading a dashboard widget may throw error "Object doesn’t support property or method of ‘find'."

SOS-DEF-2307: When using a custom field, numbered and bullet lists do not display correctly in Reading View.

SOS-DEF-2312: While viewing a test run in Single Item or Reading view, HTML tags appear in each step if run was created from a test case with rich text steps.

SOS-DEF-2375: Cross-project move of 2100 items or more will delete items instead of moving them if backing database is MSSQL.

SOS-DEF-2395: Content in rich text field is shifted to the left in Reviews Reading View (Internet Explorer only).

SOS-DEF-2399: Item of type fields do not display in Reviews Reading View.

SOS-DEF-2423: Cannot comment when highlighting a custom text field in Review Center.

SOS-DEF-2466: User who has not defined a current project by viewing will receive NullPointerException on filters with "is under" operator.

SOS-DEF-2495: Browser freezes on reviews that contain an item with deleted text that was previously highlighted.

 

NOTES FOR ON-PREMISES ADMINISTRATORS

  • Replicated version 2.13.2 is required prior to upgrade. For new installations, please use the following script for the initial installation of the Jama application (Jama Connect). The app was regression tested using Replicated 2.13.2. 

curl -sSL “https://get.replicated.com/docker?replicated_tag=2.13.2&replicated_ui_tag=2.13.2&replicated_operator_tag=2.13.2” | sudo bash -s no-auto

  • Airgap customers can download the necessary version of Replicated via https://s3.amazonaws.com/replicated-airgap-work/stable/replicated-2.13.2%2B2.13.2%2B2.13.2.tar.gz before installing the 8.25 Airgap file available in your portal.
  • Container artifacts
    • Replicated release number 1440
    • Java version (JDK_UPDATE): 8u172
    • NGINX_VERSION: 1.12.2-1.el7_4.ngx
    • TOMCAT_VERSION: 8.5.30
  • Jama Connect has moved away from managing/accessing the hierarchy for a project via cache and now leverages the database for this information. This removes the concurrency issues customers might have experienced (SOS-DEF-1756) and provides more scaling options in the future.
  • Please review the suggested database settings. Changes to the management of hierarchical data to support better scaling and concurrency operations. These changes required additional querying with less reliance on previous caching options. Changes are highlighted in this table.
    dbsettings.png
  • Database updates since 8.20

6 added table(s) 1 removed table(s) 5 table(s) with structure changes 1 table(s) with data changes

ADDED TABLES: jamaIntParam, revision_testset, jamaBoolParam, jamaStringLobParam, jamaStringParam, jamaParams

 

REMOVED TABLES fieldlayouttype

 

TABLES WITH ALTERED STRUCTURE:   

Table: traceview               Added Columns:   jamaParams_jamaParamsId   

Table: traceviewpath           Changed Columns: pathItem                Default Value: null to 0   Allows Nulls: YES to NO

Table: jamacomment_userlikes   Changed Columns: userId                  Default Value: null to 0   Allows Nulls: YES to NO

Table: fieldlayout             Added Columns:   layoutType

Table: revision_item           Added Columns:   sequence

 

TABLES WITH ALTERED DATA:

Table: patchinfo               Added Rows [7] 


Jama Software 8.20.2 Standard

Release Date: 2017/09/27

Customers who have installed 8.20.1 must upgrade to 8.20.2 for full support. 

Resolved Issues

SOS-DEF-1241: Newly created diagram does not display in IE11; instead shows broken image symbol.

SOS-DEF-2137: Add Test Case flow does not honor HTML cleaner setting.


Jama 
Software 8.20.1 Standard

Release Date Standard: 2017/09/13

8.20.1 takes the place of 8.20 for on-premises customers. Read 8.20 release notes for the full contents of this release.

Resolved Issues and Updates

SOS-DEF-2110: SQL Server customers may experience a change in Test Case Step data during an upgrade. This defect fix prevents the issue from happening. See this post for more details.


Jama Software 8.20 Standard


Released with 8.20.1

New Capabilities


WIRIS Equations Editor

The building of complex products isn't just about writing the right requirements; it's also about the correct implementation. Until now, this information lived outside of Jama Software. Now, however, we're lessening the load to get these design specifications into our system. In this release, we are introducing the WIRIS Equations Editor, a third-party plugin for the creation of equations.

    • The WIRIS Equations Editor is a visual editor that allows insertion of mathematical and chemical formulas into the rich-text editor of Items within Jama. Open the Equations Editor by selecting the Math or Chemistry icon in the rich-text editor, then create equations either using your keyboard or with the handwriting option on the sidebar.

WIRIS1.png
WIRIS2.png

    • The WIRIS Editor renders an equation by connecting to WIRIS' cloud. After connection, the image is stored in the Jama database. An active Internet connection is required for the WIRIS Editor, so this feature is not available for Airgapped installations. An additional license is required. Contact Jama Support for more information.

Reading View Revamp

Based on user research and customer feedback, we made multiple improvements to the Reading View. This included feedback from a community post, a live survey in our hosted environment in February, and research sessions in March, giving us some key insights into why reading a narrative flow matters so much and to whom it matters most. We started with some cosmetic changes:

  • Removed containers outside of your selection. When users select Items the wish to see in the Reading View, it is confusing to include other folders or sets above these in the Explorer tree hierarchy. People want to see only the Items in the container they select. This means context-sensitive reports will no longer display the containers, only the contents.
  • Removed alternating color striping in the Reading View. This cleans up the view and makes it easier to read.
  • Emphasized containers as the "headers" for the content in this view. Components/sets/folders will now show up as larger, bold text to call attention to the these versus Items inside containers. For many of our users, the component/set/folder is a heading for a set of topics that are called out in a document, and this honors that intention.
  • Added Item IDs to the Reading View as a quick access to the Single Item View. Many of our users have asked us to remove the current tree location numbering from the Reading View, as they feel it isn't easily referenced and prone to changes (every time you move Items or add Items to a project this numbering may change). For our users, the Item ID is the unique identifier for Items in Jama, so we wanted to bring that into the Reading View. We've also made Item IDs live links to the Single Item View for detailed editing.
    • Note: We plan to phase out the tree location numbering from the Reading View, but not until we create another means for indicating document hierarchy. This is something we're working on now, so keep an eye out in future release notes for this change.
  • Related Items in Reading View - Users now have the ability to access both upstream and downstream related Items in the Reading View.
    • Users familiar with Review Center will recognize this feature and the popover that displays when a related Item is selected.
    • Related Items observe user permissions regarding content access. If a user has permission to view an Item, a link will be available to display that Item's information in a popover window.
    • One of the differences with Reading View and Review Center is that the information displayed in the Reading View is live, and the related Items are no exception. The popover window is provided assuming that the user doesn't want to leave the Reading View to gain the context of an Item, but that's not always the case. For users that want to navigate to the Single Item View for a related Item, a link is available on the popover that will open the Single Item View in a separate Jama tab.
    • The related Items popover window is accessible: users can Enter to navigate to a new Jama tab with the related Item in the Single Item View, and can close the window by using the Escape key.
  • Comments in Reading View - We believe that Item comments provide valuable information to an Item, which is why we've added the comment link to the Reading View. Users familiar with the List View will recognize this feature and the popover that displays when the comment link is selected.
  • Relative Numbering in the Reading View - Users can see Item numbers relative to the container they've selected in the Reading View. This will help users who export from a container, etc., to have numbering that aligns better with exporting to MS Word.

Duplicate

The ability to duplicate Items is a key part of the editing experience and allows users to author content in Jama faster. In previous versions of Jama users would have to utilize the Reuse functionality for duplicating Items, which can be time-consuming for individual Items. Since 8.15 users have the option to use the Duplicate Item feature to quickly start a new Item in the project from the project Explorer Tree.

  • The Duplicate Item feature is limited to duplication of the Item's name, description, test steps (if applicable), and the ability to choose to include tags, attachments, and links.
  • After selecting Duplicate Item in the project Explorer Tree, the user will be introduced to a new modal that allows the user to choose whether or not to include tags, attachments, or links.
    • Tabbing is enabled for users to select or move through modal options via keyboard. The Escape Key can be used to cancel out of the menu.
    • Per Item Type, the modal preferences will be saved across sessions; however clearing your browser data will restore default options. When specific attributes (e.g., links) are not enabled for an Item Type, the option will not appear in the modal.

Accessibility Checker

    • Accessibility Checker is a new rich text plugin introduced with 8.17 that allows the user to inspect the accessibility level of content created in the rich text editor and address any accessibility issues that are found.

accessibility.png

    • If the Accessibility Checker finds an issue, it will offer a Quick Fix solution for common problems. You may enter the changes requested and select Quick Fix to apply the changes, or choose the option to Ignore the Quick Fix suggestion.

Minor Updates

  • Login Page Update - We've made an update to our login page to make it accessible via assisted technology. While we were at it, we made some visual changes that users will see the next time they log in.
  • Move Item improvements introduced in 8.12, 8.13, and 8.14 releases are now available for cross-project moves.
  • Home Page Improvements - We improved keyboard navigability of the Home Page in Jama, and made the markup more semantic. This will help users with assistive technologies and is the first step toward making Jama a more accessible application.
  • Project Clean Up - If you notice Items in a project that you can't select, either from the Explorer Tree or within search or filter results, you should clean up your project (Configure Project > Clean Up). Though it's rare, if you can’t select an Item, you may be seeing references to Items that don't exist. Deleted Items may still appear in some views, because system interruptions or transaction collisions prevented full deletion.
      1. Does not require re-indexing or downtime.
      2. Clean Up doesn’t interfere with Item history or the option to restore any deleted Items.
      3. You can confirm the completion of this action in server logs. Contact your local Jama Software administrator or Jama Support (if hosted) for this data.

Security Updates

  • Cross-Origin Resource Sharing (CORS) Improvements - We identified a potential vulnerability where CORS protection could be bypassed if environments were configured incorrectly. In order for CORS to be bypassed, customers would need to have their web browser security settings disabled in Chrome or have all sites trusted in Internet Explorer and there would need to be a cross-site scripting (XSS) vulnerability present. As a result of this potential, we're releasing these improvements to help mitigate this vulnerability for our supported customers.
    • Note: This improvement may have an impact on customers if they are not using a supported web browser.

    • Note: This improvement may have an impact on customers who are using a proxy server between the user and the Jama application if that proxy server is configured to change the user protocol from https to http. Proxy server errors can be corrected by modifying the proxy server configuration or by adding a new whitelist entry into the CORS whitelist.
  • Persistent Cross Site Scripting (XSS) Improvements - We identified a potential vulnerability where persistent XSS could take place in the application. The use of an <iframe> under certain circumstances could allow an attacker to execute arbitrary code in the browser. As a result of this vulnerability, we've removed <iframe> src from the application whitelist.
  • XML External Entity (XXE) - The application is vulnerable to XML entity injection. This allows a malicious user to upload an XML document to the application, which when parsed by the XML parser, enables read access to files available on the system hosting the application. An attacker can also instruct the server to make HTTP based requests to remote or local services.

Admin Notes

  • Due to a bug discovered in Replicated (SOS-DEF-2086: Support Bundles are incomplete), new installations of Jama should use a cURL command that does not pull the most recent Replicated release. If you are upgrading Jama, do not upgrade Replicated first. See this article for details.
  • Support for MS SQL 2016 support has been added.
  • After installation, a full re-index is required.
  • SOAP API EOL was June 30th. Access to the SOAP API will be removed upon upgrading to 8.20.
  • Jama 8.20 was regression-tested against Replicated version 2.9.3 and 2.6.0.
  • TLS 1.0 is no longer supported.

Known Released Issues

SOS-DEF-2091: Exporting content to Word from WIRIS Equations Editor will result in equations aligned differently to text than how they display in the rich text editor.
SOS-DEF-2115: The WIRIS Equations Editor is keeping the previous equation in cache for an item the user is attempting to add another equation using the Firefox browser.

Resolved Issues

SOS-DEF-581/SOS-BUG-721: The Tag Cloud does not show or update new or existing tags.

SOS-DEF-1519: If password strength is set to Strong or Good, external users cannot be invited to a Review.

SOS-DEF-1687: Coverage Report returns no results.

SOS-DEF-613/SOS-BUG-1064: Sub-Items tab displays only one level down.

SOS-DEF-1739 REST API Add or Replace operation using PATCH method fails on Items that are synced to Legacy JIRA.

SOS-DEF-1762: In the Review Center, providing feedback on an Item will make the Show related Items link disappear from all other review Items.

SOS-DEF-1817: List View column order does not follow the order set in Admin > Item Types > Configure View.

SOS-DEF-1893: Project hard delete fails for projects that don't have a root documentnode entry.

SOS-DEF-1948: When a user logs in after ending a session without logging out, the log will show two floating licenses being consumed.

SOS-DEF-1944: Seemingly random "Got an invalid reply from server that may be due to expired session. You will be logged out." while working in Jama.

SOS-DEF-1966: In the Review Center, Show Related Items is hidden in other Items after selecting Approve or Needs more work on a selected Item.
SOS-DEF-2011: Attachments with umlauts or accents in their name will show an error page when user tries to open them.

SOS-DEF-2013: The ModifiedBy and ModifiedDate fields in the database document table gets updated by Jama during migration to Jama 8.

 

Jama Software 8.14.5 Standard

Release Date: 2017/09/27

Customers who have installed 8.14.1-.4 must upgrade to 8.14.5 for full support. 

Resolved Issues

SOS-DEF-1241: Newly created diagram does not display in IE11; instead shows broken image symbol.

SOS-DEF-2137: Add Test Case flow does not honor HTML cleaner setting.



Jama Software 8.14.4 Standard

Release Date: 2017/09/15

Resolved Issues and Updates

SOS-DEF-2110 - SQL Server customers may experience a change in Test Case Step data during an upgrade. This defect fix prevents the issue from happening.

 

Jama Software 8.14.3 Standard

Release Date: 2017/07/28

Customers who have installed 8.14.2 must upgrade to 8.14.3 for full support.

Resolved Issues and Updates

XML External Entity (XXE) - The application is vulnerable to XML entity injection. This allows a malicious user to upload an XML document to the application, which when parsed by the XML parser, enables read access to files available on the system hosting the application. An attacker can also instruct the server to make HTTP based requests to remote or local services.

SOS-DEF-1182: Support for importing Word 2003 XML was removed. The primary means for supplying external XML to be parsed.

SOS-DEF-1978: Adjust configuration of XML parser. Review and disable external DTD’s in the XML parser, to prevent potential XXE vulnerabilities. Malicious users with Jama knowledge may capture and manipulate DWR calls. 
SOS-DEF-1944: Seemingly random "Got an invalid reply from server that may be due to expired session. You will be logged out." message occurs while working in Jama. 

SOS-DEF-2013: Customers that upgraded from a 2015.x release of Jama to 8.x may see an empty Modified By user field or incorrect Modified Date due to procedure responsible for updating system URLs on items with rich text images during the upgrade. The upgrade step has been fixed so future upgrades will not be affected. The modified by/date information is still safe within the item's version and will be replaced with this upgrade.

Jama Software 8.14.2 Standard

Release Date: 2017/6/29

Resolved Issues and Updates

Cross-Site Request Forgery (CSRF) Improvements - We identified a unique case where a CSRF attack could be successful if environments were configured incorrectly. These improvements are limited to the application and REST APIs, and have been independently tested by a third party penetration test prior to release.  Customers who have their web browser security settings disabled in Chrome or have all sites trusted in Internet Explorer may be impacted by this. As a result of this potential, we're patching with these improvements to help mitigate this vulnerability for our supported customers.

 

Cross-Origin Resource Sharing (CORS) Improvements - We identified a potential vulnerability where CORS protection could be bypassed if environments were configured incorrectly. In order for CORS to be bypassed, customers would need to have their web browser security settings disabled in Chrome or have all sites trusted in Internet Explorer and there would need to be a cross-site scripting (XSS) vulnerability present. As a result of this potential, we're patching with these improvements to help mitigate this vulnerability for our supported customers.

  • Note: This improvement may have an impact on customers if they are not using a supported web browser.

  • Note: This improvement may have an impact on customers who are using a proxy server between the user and the Jama application if that proxy server is configured to change the user protocol from https to http.  Proxy server errors can be corrected by modifying the proxy server configuration or by adding a new whitelist entry into the CORS whitelist.

 

SOS-DEF-1817: In the admin panel, default column List View order can be set for individual item types. Due to this defect, List View column order does not follow the order set in Admin > Item Types > Configure View.

 

Project Clean Up - If you noticed items in a project that you can't select, either from the Explorer tree or within search or filter results, a system re-index was required, resulting in scheduled downtime. Now, though it's rare, a project administrator can clean up a project (Project > Configure Project > Clean Up) if you can’t select an item or if there is a reference to an item that doesn't exist. This was introduced to reduce need for downtime due to re-indexing. 

    1. Does not require re-indexing or downtime.
    2. Clean Up doesn’t interfere with item history or the option to restore deleted items.
    3. You can confirm the output of this action in server logs. Contact your local Jama Software administrator.


Version: 8.14.1

Release Date: 2017/4/21

Build Date: 2017/4/20

Resolved Issues

SOS-DEF-1808: PATCH fails when item type contains a rollup field.

Version: 8.14

Release Date: 2017/3/29

Upgrade to 8.14 will run a database patch named ”Set sort order for TestSetCases” that can take a while depending on the number of items in Test Center.

New Capabilities

  • Move Item Notification Update - When users change Explorer Tree hierarchy by moving items in the Tree or from List View, the "Success" notification now provides the location where the item(s) moved. The notification lasts 10 seconds to allow users time to read and process this additional information.
  • Move Item Undo - The user now has the option to undo the move during the success notification window. Selecting Undo Move in the notification window restores the Explorer Tree hierarchy and moved items return to their original location.
  • Move Item Activity Stream Event Updates - Multiple changes were made to the Activity Stream to provide users with more information and context around item moves. These changes are not retroactive (movements before the installation of 8.14 will not be reformatted). For new moves after installation of 8.14, many improvements will be available to users:
    • Move Item event entries in the Activity Stream now provide the user with a path to the location where the item was moved from. A link is available for navigation to the location and the container's navigation path is provided upon hovering over the location link. This information becomes particularly useful for projects that use generic component/folder naming structure for consistency.
    • Detail popover for Move Item entries displays all of the items that were moved. Items in Detail view now have links that take the user to the item's single item view.
    • View Moved Items link enables users to view all of the items moved from a particular location in the List View. This feature allows the user to select items and move them if desired. Now that the user has moved from location in the event entry, this provides a path for moving items back to their original location after the Undo option is no longer available.
    • For bulk moves via the List View, Move Item events in the Activity Stream now "roll up" to one activity per location item(s) were moved from. All subitems are reflected in these rollups, so users can understand the gravity of a particular move event and/or find subitems and better understand the context of why they moved.
    • Move Item event entries now show the user when a container and its child items have been moved. This provides additional context for a container move and distinguishes it from several items selected and moved from the List View.
    • Move Item entries in the Activity Stream respect user permissions - If a user doesn't have access to the location an item was moved from, the location information does not show up in the activity stream entry.
  • MS Edge Support - Jama now supports the Microsoft Edge web browser.
  • Jama's Rich Text Editor (CKEditor, now version 4.6.1) has been updated with this release. This update resolved a number of existing defects (see Resolved Issues).
  • REST updates to test endpoints
    • Testruns include the version of the test case it was created from and the current version of the test case.
    • Each testrun indicates its sort order within the test group it belonged to when the test cycle was created or edited.
    • Test Cycles include version endpoints.
    • New options (test plan ID, test cycle ID, test case ID) to retrieve testrun.
  • REST API updates include PATCH, linked objects and updates to picklistoptions. See REST development page REST API | Jama Software for details.
  • Read Only fields have new configuration option Allow API Overwrite, allowing the update of read only fields via REST API.
  • Replicated deployment: we have reduced the privileges required for running containers and files and directories that were previously owned by root.
  • Trace View updates - No matter where you are in the Trace View, the data displayed needs abundant context and clear ties to the rest of the work in your Jama system. The Trace view continues to see refinement this release, with enhancements to make the navigation of related items more meaningful with richer context.
    • 1.png
    • 2.png
    • 3.png
    • When an item is selected, the Trace View highlights that item and all its lineage. The selected item becomes darker blue, and all upstream and downstream related items are highlighted in light blue. These highlights remain as the user navigates up and downstream, enabling intuitive navigation of the entire thread of an item's relationships in all directions.
    • In the screenshot below, one item CL3-MR-2 is selected. Here you can see one level of downstream items related to CL3-MR-2 highlighted in light blue.
    • Below the user has navigated an additional level downstream from CL3-MR-2, where more lineage is highlighted. By keeping related items highlighted, this allows the user to see the full decomposition or origin of the item selected as they navigate.
    • The selections are also easier to manage. Beneath the Trace View name see the number of items selected, and use the Clear All button to remove all selections and accompanying highlighting.
    • See more context for the items in view by clicking on the ID to open the detailed side panel. This side panel now display images, html, and tables. If the full item details are still required (e.g. for detailed authoring), click on the item ID from within the side panel to see the full item in it's own tab.
    • 4.png

Resolved Issues

SOS-DEF-203/SOS-BUG-640: Review Center Next button does not work in Chrome-IE for customers in specific Time Zones.

SOS-DEF-380/MAIN-BUG-319/SOS-BUG-330: Using two hierarchy options for Excel import ("Import hierarchy based on indented cell" and "Color cells indicate folder or parent item") flattens hierarchy within folders.

SOS-DEF-384/MAIN-BUG-377, SOS-BUG-367: Items cannot be batch converted to Text.

SOS-DEF-400/MAIN-BUG-322/SOS-BUG-339: "Items I haven't marked" filter in Review Center takes user to the wrong item if the item gets marked.

SOS-DEF-459/MAIN-BUG-19/SOS-BUG-284: Plain text box does not honor return carriage on export.

SOS-DEF-516/SOS-BUG-475: When archived, Test Runs may still show as unarchived because of slow indexing.

SOS-DEF-550/SOS-BUG-832: Relationship Status column does not export to Excel from Reading View or Coverage Explorer.

SOS-DEF-562/SOS-BUG-973: Jama allows duplicate item type keys.

SOS-DEF-586/SOS-BUG-780: Only the first level of result sort order is applied in Filter results.

SOS-DEF-601/SOS-BUG-943: The wrong project is shown in the Save Test Run Defects dialog box.

SOS-DEF-617/SOS-BUG-1092: Cannot add an !answer or a !decision to Collaboration Stream when the mentioned item has been deleted.

SOS-DEF-624/SOS-BUG-680: Test Cycle dropdown shows inactive and/or deleted Test Cycles.

SOS-DEF-671/SOS-BUG-706: User Import Plugin notification email contains malformed URL.

SOS-DEF-675/SOS-BUG-742: Test Run Status indicator lights do not include "In Progress" status.

SOS-DEF-698/SOS-BUG-939: If a computer is in a certain timezone or language, creating a review hangs at the last step.

SOS-DEF-709/SOS-BUG-1067: When test cases are exported to Word and Excel, HTML is included if rich text is enabled for test steps.

SOS-DEF-714/SOS-BUG-1098: After editing a Test Case in single item view and choosing Save and add another, the new Test Case tab is a blank page.

SOS-DEF-754/SOS-BUG-928: Using inline editing to edit Text Field or Text Box updates ModifiedDate and LastActivityDate even where there is no actual change.

SOS-DEF-932/SOS-BUG-875: Changing the items that are currently in review when there is no version created can cause highlight comments to go out of range and a browser freeze when loading the review.

SOS-DEF-1008: A comment that stems from a deleted item can not be deleted in the Collaboration Stream.

SOS-DEF-1012: When an item is removed from the Review Center, the comments that were previously on that item can no longer be deleted.

SOS-DEF-1067: Velocity reports using report_relate and report_tag criteria like "All Item Details" won't display relationships and tags.

SOS-DEF-1084: Test Run duration < 1 second is displayed as 02:00:00 in Test Center.

SOS-DEF-1111: No "More..." link displayed for Test Cases when there are more than 100 Test Cases in the Test Plan, but no Test Group has more than 100 Test Cases.

SOS-DEF-1126: Clicking the edit pencil icon on a description field on inline-edit List View causes the homepage to be loaded and edits to be lost.

SOS-DEF-1154: Cannot create a user with an email address that has an apostrophe: the email is considered invalid.

SOS-DEF-1158: Querying /activities/?objectType=TEST_CYCLE, TEST_RUN, TEST_CASE, or TEST_RESULT with REST API returns no items.

SOS-DEF-1163: Using a Round-trip report with a custom item type that has sub items returns an empty sheet. SOS-DEF-1173 Deleted comments from an item count against the total in the list view.

SOS-DEF-1188: Project hard delete fails for projects that don't have a root documentnode entry.

SOS-DEF-1195: Indentation of lists is not kept in rich text fields after initial Save.

SOS-DEF-1229: Collaborators can go through process of creating an item in Project area but are then unable to save.

SOS-DEF-1233: Sets can be created with an invalid set key with the REST API. SOS-DEF-1237 Unable to upload attachments after editing Attachment field on Attachment item type.

SOS-DEF-1270: Open In New Tab right-click menu option is present for Test Plans. Users should not be able to open multiple Test Plans simultaneously.

SOS-DEF-1272: When adding a Defect to a Test Runs, required rich text fields can be bypassed without adding text.

SOS-DEF-1295: Welcome to Jama' modal does not recognize valid email address with .auto suffix.

SOS-DEF-1338: The "# of items haven’t marked" filter in Review Center is different from the actual filter results returned.

SOS-DEF-1400: User search is scoped to include unintended fields like a group's CreatedBy and ModifiedBy user.

SOS-DEF-1407: Rest API rejects valid URLs for URL field types.

SOS-DEF-1414: Deleting item fails with "could not execute batch" message.

SOS-DEF-1430: IE11 throws a minified exception when selecting Related links.

SOS-DEF-1456: Calculated field won't update if the pick list values being calculated are edited through the List View in-line edit.

SOS-DEF-1458: Directory permissions on Jama 8 Replicated hosts are too broad.

SOS-DEF-1463: Reviewer/Approver stats shows progress above 100%.

SOS-DEF-1501: Removing and replacing a pick list value on deleted items makes deleted items visible in filters.

SOS-DEF-1504: Older version of Test Case does not display Test Steps after selecting Make Current in version compare.

SOS-DEF-1528/SOS-DEF-1557: When a Review has no Related Items, when publishing a new revision an error is thrown (will vary by browser). 

SOS-DEF-1529: Single Item View comment count incorrectly includes active comments in a deleted thread.

SOS-DEF-1538: Clicking through pages in Review Center single item view throws an error.

SOS-DEF-1566: Calculated fields don't update following imports of the values used for the calculation.

SOS-DEF-1589: Jama sends data to New Relic from Swagger documentation, even if the instance was never configured to use New Relic.
SOS-DEF-1598: Some processes run as root that do not require such privileges. 

SOS-DEF-1627: Calls to REST API abstractitems endpoint does not return all attachments.

SOS-DEF-1650: In List View, calendar pop-out is cut off if column is not widened.

SOS-DEF-1712: Selecting Needs More Work throws Javascript error when reviewing an item with related items.

SOS-DEF-1722: Imports and Batch Transition of workflows is 5-10x slower than in previous versions.

Resolved as part of Rich Text Editor upgrade:

SOS-DEF-557/SOS-BUG-902 Tables cannot be deleted from a text box if they are the only content in the field.
SOS-DEF-599/SOS-BUG-912 Copy function is not available as an icon or as a right click pop-up menu when editing rich text.
SOS-DEF-751/SOS-BUG-897 Copying from static rich text and pasting into a rich text field creates inconsistent font sizes.
SOS-DEF-500/MAIN-BUG-299/SOS-BUG-281 Rich text editor will encode some special characters with HTML, which disables the ability to search on those characters.
SOS-DEF-503/SOS-BUG-465 Very large images in CKEditor have trouble displaying after being uploaded.
SOS-DEF-986 When cutting (Ctrl/Cmd+X) and pasting as plain text in a description field, edits are not saved to item.
SOS-DEF-618/SOS-BUG-1097 Attachments cannot be linked to Test Runs description through the rich text editor.


Dropped Issues

As part of upgrading the Rich Text Editor in 8.13, the following defects have been tested and deemed intended behavior. As a result, Jama is no longer tracking these defects or targeting them for resolution.

SOS-DEF-349/SOS-BUG-572 After upgrade to 2014.2, paragraph spacing is removed within rich text editor.
SOS-DEF-670/SOS-DEF-702 A line break will be inserted after each rich text field when exporting.
SOS-DEF-956 Cannot copy and paste both text and images to a rich text field simultaneously, only individually.
SOS-DEF-1255 Mixing left-to-right languages with right-to-left languages in a sentence causes words to be moved from their original position when pasted to a rich text field.

As part of a recent defect cleanup activity, the following defects have been deemed unreproducible in Jama as of 8.10.2. As a result, Jama is no longer tracking these defects or targeting them for resolution. Should you find one of these defects to be present in 8.14+, please contact Jama Support.

  • SOS-DEF-99/SOS-BUG-1109: QueueDeletedDomainObjects job fails when deleting project, so projects remain in database.
  • SOS-DEF-413/SOS-BUG-467 Review Center Workflow and Item Type Workflow do not work together. User Guide has been corrected to state this.
  • SOS-DEF-436/SOS-BUG-223/MAIN-BUG-84 Unable to delete groups after enabling LDAP.
  • SOS-DEF-445/SOS-BUG-424 Javascript error will occur when switching among items of the same item type or editing an item if the type has no Comments widget enabled.
  • SOS-DEF-504/SOS-BUG-503 Suspect links cannot be cleared on items with workflow locks. Suspect links will be cleared if at least one of the items is writeable.
  • SOS-DEF-554/SOS-BUG-882 Searching in user fields will not display all the users in the first page if the user base exceeds 100.
  • SOS-DEF-587/SOS-BUG-790 java.lang.ClassCastException error will occur when importing item with required field.
  • SOS-DEF-778/SOS-BUG-693 Removing a child item does not update "Has Child" column in Round Trip export.
  • SOS-DEF-999 Indexing fails for items containing the Unicode Line Separator character (U+2028 or 0xe280a8).
  • SOS-DEF-1080: New Test Groups are not visible when editing a test cycle unless page is reloaded.
  • SOS-DEF-1141: Selecting the View in List button inside an unsaved filter will close the filter window and open the Project Dashboard tab.
  • SOS-DEF-1142: Cannot select Make Decision on an Open Decision item when the item has been moved to a different project.

Jama 8.10.4 Standard

Release Date: 2017/08/03

Customers who have installed 8.10.3 must upgrade to 8.10.4 for full support.

Resolved Issues and Updates

XML External Entity (XXE) - The application is vulnerable to XML entity injection. This allows a malicious user to upload an XML document to the application, which when parsed by the XML parser, enables read access to files available on the system hosting the application. An attacker can also instruct the server to make HTTP based requests to remote or local services.

SOS-DEF-1182: Support for importing Word 2003 XML was removed. The primary means for supplying external XML to be parsed.

SOS-DEF-1978: Adjust configuration of XML parser. Review and disable external DTD’s in the XML parser, to prevent potential XXE vulnerabilities. Malicious users with Jama knowledge may capture and manipulate DWR calls. 

SOS-DEF-2013: Customers that upgraded from a 2015.x release of Jama to 8.x may see an empty Modified By user field or incorrect Modified Date due to procedure responsible for updating system URLs on items with rich text images during the upgrade. The upgrade step has been fixed so future upgrades will not be affected. The modified by/date information is still safe within the item's version and will be replaced with this upgrade.

Jama 8.10.3 

Release Date: 2017/07/06


Resolved Issues and Updates

Cross-Site Request Forgery (CSRF) Improvements - We identified a unique case where a CSRF attack could be successful if environments were configured incorrectly. These improvements are limited to the application and REST APIs, and have been independently tested by a third party penetration test prior to release.  Customers who have their web browser security settings disabled in Chrome or have all sites trusted in Internet Explorer may be impacted by this. As a result of this potential, we're patching with these improvements to help mitigate this vulnerability for our supported customers.
SOS-DEF-1944: Seemingly random "Got an invalid reply from server that may be due to expired session. You will be logged out." message occurs while working in Jama. 

Version: 8.10.2

Release Date Standard: 2016/12/08

This release is a patch for 8.10.1 to resolve a performance issue. 


Resolved Issues

SOS-DEF-1539: Jama installation not honoring memory configuration and using Java's default maximum memory configuration.

Version: 8.10.1

Release Date Standard: 2016/11/30

Important Note for JIH Users: Due to security enhancements to our SOAP API, older versions of the JIH (pre 4.5.7) may not sync properly after the 8.10.1 update. Please upgrade your JIH to the latest version available here to take advantage of our REST API and resume syncing. For more details on the SOAP API security change, see the Jama community post.

Important Note for Velocity Report Users: The Velocity reporting engine has been updated to version 1.7, and as a result custom Velocity reports using macros will need to be modified to function correctly. Previously it was possible to pass a reference to a variable to a macro and #set that variable inside the macro. See VELOCITY-681 for technical details. We have an example available of the how to make this change to your templates.

New Capabilities

  • The New Trace View is here! With this release we have completed the core set of functionality for the Trace View. Starting in 8.10.1 users can trigger a Trace View from a list and immediately see items connected upstream and downstream. Missing relationships, based on the relationship rules, are highlighted. Take action immediately—correct missing relationships by relating existing items or adding new ones. Adjust visible fields, reorder columns, and export your data to a .csv file to be further analyzed. Returning to the view is simple with the ability to save, bookmark to your homepage, and share the URL with other team members.

trace.png

  • Multi-Organization Check - Jama on-premises customers that originally installed Jama versions prior to version 4.3, available spring of 2014, had the option to add organizations which operated much like a separate instances in Jama. These were typically used as a sandbox or sample data set. Jama removed the ability to add an organization with version 4.3 and are looking to end of life this capability in spring of 2017. Admins that receive this message should contact their system administrator of Jama support.
  • Relationships in Review Center - When creating a review, you can include the specific set of related items you need users to analyze. You can now filter by the item type in the review, the item type it's related to, and the relationship type that links them.

  • Bookmarking Saved Views - Jama users can now bookmark frequently used views on their home page. By using the bookmark icon next to Recently Viewed locations in Jama, users can keep a curated list of workspaces they return to most. From within the Trace View (in Open Preview), saved Trace Views can be bookmarked directly from the page.

  • Access to Versioned Relationships - Versioned relationships previously only viewable via Review Center are now accessible via the REST API, Baseline Compare, Exports and custom Velocity reports.
  • REST Management of User Groups - Groups can now be created, updated and removed via the REST API.
  • Added Support for High Security Mode in New Relic - New Relic has a "High Security Mode" which limits the type and amount of information their agent gathers from the customer server and sends to New Relic's servers.

Admin Notes

  • Customers must upgrade Replicated to the latest available build (at least 2.2.0) before this release will appear in your Jama Admin console (See Server Administration > Installing, Upgrading, and Migrating Jama > Migrating Jama > Migrating from Replicated 1.x to 2.x in the User Guide; if you are already at 2.1, use the command curl -sSL https://get.jamasoftware.com/docker | sudo bash -s no-auto).
  • Jama needs to be re-indexed after upgrade.
  • Customers upgrading their on-premises instance of Jama from 2015.1 or older will need to upgrade to Jama 2015.2 or newer prior to upgrading to Jama 8.10.
  • MS SQL 2012 will no longer be fully supported after January 2017. See Supported Software for supported environments.
  • An update to Jama 8.10 has improved REST API URL requirements to validate correct formatting. As a result, REST requests will no longer allow for the passage of extra forward slashes in URL paths. This may cause an error for some customers’ custom integrations built utilizing Jama’s REST API. To review the latest documentation on the Jama REST API visit http://dev.jamasoftware.com/rest.
  • We have changed the way our SOAP API accepts requests to enhance security. If you have a Jama SOAP API integration, please see our the Community Post for more information on what actions you can take.
  • Due to some internal security upgrades, the Remember Me? functionality has been removed from the login page. 

Resolved Issues

SOS-DEF-180/SOS-BUG-620: Irrelevant tooltip displayed on the Rich Text Editor.

SOS-DEF-480/MAIN-BUG-210/SOS-BUG-253: Description typeface in Word Export template does not export.

SOS-DEF-483/MAIN-BUG-329/SOS-BUG-256: Export to Excel does not include the Version or Current columns for Baselines.

SOS-DEF-688/SOS-BUG-829: Hyperlinks from Excel and Word don't work if Jama has SSL active.

SOS-DEF-799/SOS-BUG-1020: Delete project on larger projects fails due to a foreign key constraint on itemrelationshipstats table.

SOS-DEF-1000: Javascript can be added to Notice on Login Page box, potentially preventing the front-end from rendering and opening an XSS vector.

SOS-DEF-1001: Extra lines between description field and the next field in Export to Word export.

SOS-DEF-1147: Downstream items link may take user to the project dashboard instead of a list of downstream items.

SOS-DEF-1196: REST API throws null pointer exception when passing an empty array in a multi-select field.

SOS-DEF-1204: Reusing items with Rollup field retains % in destination item.

SOS-DEF-1212: Loading the reviews page can take upwards of 1.5 minutes for medium to large datasets when public reviews are enabled (due to getAllMyReviewsByStatus.dwr). As a result of this fix, review moderators will no longer be presented with the total comment count for their reviews. We felt value in speeding the overall loading of the page for all users outweighed the count which was useful only in specific situations.

SOS-DEF-1227: Using European date format may cause discrepancy between what is chosen in a Filter date picker and what is saved.

SOS-DEF-1248: Required flag does not allow saving of item if using single item edit view.

SOS-DEF-1251: A filter created on an Item field label with a special character will return a JSON error when using View in List.

SOS-DEF-1304: Hosted 8.7 help guide has 8.6-H on "Welcome to Jama" page.

SOS-DEF-1339: Deleting items from Reading View will delete items in parent set as well.

SOS-DEF-1348: Commenting on a closed review incorrectly states comment has been saved.

SOS-DEF-1371: Airgap instances that have specified a context path link to the Hosted help guide.

SOS-DEF-1378: Pendo (analytics tool) is enabled for Airgap installations.

SOS-DEF-1382: Missing permission node keeps Test Runs from showing up in Test Cycles.

SOS-DEF-1398: DNC updates cause server error when deleting attachments from project.

SOS-DEF-1429: Items not included in a filter are deleted when deleting items from a filtered list view.

SOS-DEF-1511: createdDate, modifiedDate, and lastActivityDate return 400 with PUT on item, even if date is matching.

Version: 8.4.2 standard

Release Date: 2016/09/29

Customers who have installed 8.4.1 must upgrade to 8.4.2 for full support.

Resolved Issues


SOS-DEF-1378: Pendo (analytics tool) is enabled for on-premises installations.


Version: 8.4.1 Standard

Release Date: 2016/07/19

Customers who have installed 8.4 must upgrade to 8.4.1 for full support.

Resolved Issues
RELEASE-DEF-752: The Jama application may time out during installation and not provide a clear error message.

Version: 8.4 Standard

Release Date: 2016/07/14

If you haven’t yet installed Jama 8.x, visit our upgrade page to start the process. Upgrades from 8.x can be downloaded via the Admin Console within Jama.  

New Capabilities

  • Airgap installation is now available.
  • Relationships in Review Center
    When creating a review, you can include the specific set of related items you need users to analyze. You can filter by the item type in the review, the item type it's related to, and the relationship type that links them.

Resolved Issues

(updated 2016/08/03)SOS-DEF-104/SOS-BUG-1144: Bulk creation of relationships slow as total number of relationships in the system increases when using SQL Server.
SOS-DEF-519/SOS-BUG-627: Working with Test Plans becomes very slow as the number of Test Runs increases.
SOS-DEF-561/SOS-BUG-945: In an exceptionally large enterprise environment, Bidirectional Traceability query can run for much longer than expected.
SOS-DEF-649/SOS-BUG-1038: If there are more than 3200 attachments in a project, attempting to Link to an existing attachment in the rich text editor takes several seconds.
SOS-DEF-684/SOS-BUG-789: JIRA Connector will delete and recreate all custom field values in the documentcustomfieldvalue table on every sync, causing a large churn in ID values.
SOS-DEF-738/SOS-BUG-792: User with correct Read permissions receives error when trying to clear a suspect link.
SOS-DEF-800/SOS-BUG-1035: Reverting to an older version of an item that is using a deleted pick list value will show that deleted value in the new version.
SOS-DEF-948: Even if Allow non-Admins to delete items and containers is disabled, users are still able to delete them if more than one item is selected in List View.
SOS-DEF-1107: Concurrent long-running batch operations can cause Jama to hang (SQL Server only).
SOS-DEF-1108: Viewing Test Runs or creating Test Cycles from Test Plan is very slow with large number of Test Runs and Test Steps in the dataset (SQL Server only).
SOS-DEF-1110: Batch Update Test Run Status performance gets worse as more data is stored in Jama (SQL Server only).
SOS-DEF-1113: Organization Name is truncated in application header if more than 34 characters.
SOS-DEF-1152: TLS is misspelled in Admin Console UI as TSL.

Admin Notes

  • You need to upgrade to Replicated 2.0  before this release will appear in your Jama Admin console (See Server Administration > Installing, Upgrading, and Migrating Jama > Migrating Jama > Migrating from Replicated 1.x to 2.x in the User Guide).
  • Replicated 2.0 introduces a time_out for the installation and upgrade process that is set to 10 minutes. If the installation and upgrade process takes more than 10 minutes, an error message shows up on Admin Console. Please check contour logs in /logs/tomcat/contour/contour.log to make sure installation is actually complete. Do not hit Start until the installation/upgrade is compete. We are currently working on this defect (RELEASE-DEF-752) and a fix will be available soon. 
  • There is a known defect (SOS-DEF-1225) in Replicated 2.0 that affects RHEL environments. The Support Bundle will not include Jama container log files. This defect will not impact the installation process or Jama’s performance. However, during troubleshooting you will need to send those log files separately, which are located in the application server in the /logs/tomcat/contour directory. To avoid the issue, install Docker directly from the Docker repository or let the Replicated-led Jama installation process install Docker.

Other Notes

Server Requirements/supported software changes

 

Version: 8.1 Standard

Release Date: 2016/05/25

As a Jama customer, you now have two options for upgrading Jama due to our new deployment model and the availability of two channels. Our Express channel offers the same speed of deployment as our Hosted version, while the Standard channel offers the stability of features often needed in an Enterprise environment. Visit our Success site for an overview. If you haven’t yet installed Jama 8.x, visit our upgrade page to start the process. Upgrades from 8.x can be downloaded via the Admin Console within Jama.

You can find the supported software for Standard here

>New Capabilities:

 

  • Upgraded contextual URLs Add bookmarks/links to places you want to save. Share links to filtered views and search results with others. This means the back button works as expected. The contextual URLs will apply to specific views:
    • Home
    • Project
    • Item
    • Filters
    • Explorer (Component, Set, Folder)
    • Releases
    • Stream and Reviews already have URLs
    • Don't forget to clear your browser cache so that the new routing works.
  • New Single Item view The single item view has been enhanced with more intuitive interactions, improvements to the editing flow, and a modern look. Users can quickly edit items by double-clicking anywhere on the item content, without locating the edit button or opening a separate window. While in edit mode, users can update calculated field inputs and see the results updated in real time. This is especially useful if users have calculations such as Weighted Shortest Job First on an item, and wish to see the updated output values with different inputs. The tags, links, and attachments functionality has been moved from behind tabs (widgets) and into the main item body. This valuable data is now easily scannable and editable in one spot at the bottom of every item. Together these updates streamline the process of adding and editing data in Jama.
  • Single item menu with activity counts See context for Jama items at a glance with the new item menu. The menu appears in the upper right corner of all items and can be configured to show data relevant to that data type. Each button corresponds to a widget of the item, such as relationships or comments. The bottom tabs panel is hidden by default, increasing room to read the item's content until more data is desired. Activity counts indicate what data may be most relevant, and clicking opens/closes the corresponding tab.
  • Quick Filter from any list view, quickly combine many filtering options visually, without writing complex logic. We have released the following new facets:
    • Author
    • Keyword
    • Project
    • Coverage
    • Item Type
    • Last Modified

Calculated field additions

    • Related items calculations: Users will be able to setup calculations on an item type that will look at related items, pulling in values from integer or picklist fields on related items (limited to one item type).
    • Weighted shortest job first (WSJF) calculation: This calculation will allow you to combine multiple factors of value to help make more informed decisions around prioritization of your backlog. The calculation weighs items with a higher value and lower effort as the thing to work on next.
  • Coverage Facets Jama uses Relationships and Relationship Rules to help users better manage coverage. With the new Coverage facet users can now directly from any list or reading view filter based on the rules defined for the project. For example, if you are looking at a list of requirements, and you want to quickly know which requirements are missing downstream items based on the rules defined, you can now filter on "Missing Downstream." This will evaluate the rules defined for the project to determine what qualifies and will filter the view. If there are no rules defined only the facets for "Is Suspect" and "Causing Suspect" will show.
  • Relate to existing from List and Reading view We have added the ability to "relate to existing" in the List and Reading views. 
  • Search improvements Search has been improved to bring forward more relevant results.
    • Search Service (Elasticsearch) We have made improvements to the search service by using industry leading technology to decrease indexing time 10x and improves current throughput of concurrent activities.
    • Search Projects We've added search to the Change Project module. No more scrolling through your complex project list—as you type, the available projects will be scaled down.
    • Search results will no longer contain items only containing the Boolean operators AND, OR, NOT (i.e. lowercased "and," "or" and "not" will be ignored).
    • Wildcard searches are possible at beginning or end of words. Now, if you search for TRIM, you'll get results that include Trim0 through Trim9, etc. as well as OSCTRIM. Asterisks are not required in the Search box for this functionality.
    • Search by field label means users will no longer be required to know the database field name and can search by the label they see in the UI. As an example, if you want to search for items with Story Points equal to 5, you'll search Story_Points: "5". Note that an underscore is required if there is a space in the field label.
    • Grouping for more complex queries is now allowed with parentheses.
    • Search custom fields: previously, Jama custom field search would only include results from custom text fields. This will allow users to quickly find the information they are looking for.
  • User home page is now the default landing page When you launch Jama you will have a personalized home page including active reviews you’re a part of, comments directed at you, improved search box, and a list of your recent projects.
  • Diagram Editor Update We have updated the diagram editor with new shapes including UML objects, BPMN for Business Process Modeling and SysML. Overall ease-of-use is drastically improved with new editing tools and options. Text within shapes will now automatically wrap.
  • Rich Text and Images in Test Steps Rich text can now be used in test steps, including the ability to insert images in test steps. This requires a change via Admin > Item Types > Test Case [or any custom types enabled with this widget] > Configure > testCaseSteps. Select the pencil to edit the field and check the Allow Rich Text option and Save. (Note that the test steps are not yet highlightable in Review Center.)
  • REST API (versions, baselines, groups, releases) The Jama REST API can now be enabled for on-premises customers. The Jama REST API has been designed to provide developers with a standardized and straightforward experience for integrating with Jama. Accessing your Jama data is now easier than ever with our new REST API. Building custom integrations and reporting are just a few of the enhanced capabilities you can now enjoy as part of your Jama subscription. For instructions on enabling the REST API please visit our developer site. With the availability of REST, this means that the SOAP API EOL is imminent. Full support for SOAP ends December 31, 2016. (More details on this to come!)
  • Jama On-Premises Admin Console With the 8.0 release, we’re launching a new Jama On-Premises Admin Console. This provides a consolidated view of your on-premises installation including configuration management, customizations, service monitoring, support bundle generation, upgrades, and snapshots.
  • Enhanced Image Security With an update to our reporting engine, images are now embedded into reports and image security is enabled. Note: If you use the Jama Integration Hub, images embedded in a rich text field in Jama will no longer be visible in JIRA for unauthenticated users when synced over via the JIH.

Additional Admin Notes

We have changed how some behind-the-scenes features work and have added support for additional tools. 

  • adjusting database connection strings
  • importing external certificates (Java key store)
  • More DIV styling is allowed in CKEditor (note that Office exports may differ from in-Jama rendering)
  • E-mail templates can be edited, but the directory has changed; see this article for more information
  • Root user can edit the attachment whitelist
  • Root user can allow bypassing of custom MIMEtypes when unknown
  • Jama/Nginx can be closed for maintenance
  • Log Configuration is available for search/ElasticSearch Containers
  • Support Bundle will include 3 thread dumps taken in 5 second increments
  • Thread dumps can also be taken manually on the command line



Security Updates

  • Upload of HTML and Javascript Due to security concerns we are no longer allowing direct upload of HTML or Javascript files, although they can still be zipped up. Any unrecognized file format will have its content type changed to disallow rendering in the browser, so some things that used to work in-browser may not for new attachments. HTML & Javascript files previously uploaded will continue to be accessible.
  • Changes in the ability to use iframes In the interest of better security, we’ve introduced a few changes to the rich text editor in both the item editor and the collaboration stream. In previous iterations of the rich text editor, a user could include a hidden iframe element in the text of a comment or description, which could employ a link to load potentially malicious content from another domain. Because Jama does not have access to this content until the link is clicked, validating its contents to prevent these attacks is not possible. Instead, we are removing the ability to load this content within open Jama pages by making the following changes: Users can no longer use the target attribute of the a element to target specific elements in Jama. Top-level targets, such as a new window, may still be used.The iframe element will no longer allow the name or id elements. Most users will not be affected by these changes. However, if you have inserted links in rich text fields that interact with iframes or other elements on the page, these interactions will no longer work after the item in has been updated.



Other Notes
Known issues:

  • Your Jama server must be able to access the Internet, at least through a proxy, during the installation process. Air Gap installation is not supported with the initial Standard release. 
  • Customers who have edited files within the Jama .war file in the past will no longer be able to do this. Generally, we are working to support those changes that we know about within Jama, but certain changes will not be possible with the initial release. We plan to address them in subsequent releases: changes to header color to differentiate among different instances of Jama and changes to Tomcat configuration files (such as server.xml).

Server Requirements/supported software changes
Beginning with this release, customers using Jama on-premises will be required to install Jama in a Linux environment with a MySQL (recommended) or Microsoft SQL Server database. We believe a standard approach for configuring Jama environments will provide the greatest benefits to our customers utilizing Jama within their own environments.

Resolved Issues

SOS-DEF-109/SOS-BUG-997: Deactivated users can still access SOAP API.
SOS-DEF-111/SOS-BUG-884: Inserting more than 4,000 characters into a Test Case Step throws an error and freezes Jama.
SOS-DEF-113/SOS-BUG-1031: In Review Center, looking at item details by selecting the title, then selecting Back to Review, will break the filters and show only that single item.
SOS-DEF-116/SOS-BUG-825: IE Users not using EN_US locale will get 500 Error message when first logging into Jama.
SOS-DEF-118/SOS-BUG-817: Attachments and images are not deleted from server when deleted in the UI, so they surface in Attachment and Links interfaces. With fix, files will remain on server but not in the UI.
SOS-DEF-119/SOS-BUG-1054: Health Report doesn't show data for Projects when there are a large number of active projects.
SOS-DEF-121/SOS-BUG-487: Uploading an attachment in IE with a particular setting enabled results in the full directory path as the attachment name.
SOS-DEF-122/SOS-BUG-635: Rich text fields do not load in editing mode, and the error "The HTML editor is not ready yet" may pop up.
SOS-DEF-123/SOS-BUG-796: Images embedded in content when copied are stored the same way when copy-and-pasted.
SOS-DEF-124/SOS-BUG-836: Test Run comments are visible in the Stream to all users, regardless of permissions.
SOS-DEF-126/SOS-BUG-984: Tasktop Migration Plugin throws optimistic locking exception and halts when there are other activities on the items.
SOS-DEF-128/SOS-BUG-994: Deactivated Users can still access REST API.
SOS-DEF-129/SOS-BUG-208/MAIN-BUG-347: During the Round Trip process, if a spreadsheet cell is empty, the old value will be kept when imported back into Jama.
SOS-DEF-134/SOS-BUG-329/MAIN-BUG-341: Text bounding box doesn't wrap text inside of a shape.
SOS-DEF-143/SOS-BUG-533: Unassigned does not populate in a field of type User.
SOS-DEF-144/SOS-BUG-538: License threshold notifications fail to send, but a null pointer exception surfaces in logs.
SOS-DEF-151/SOS-BUG-804 : Items in a set disappear when batch operations fail.
SOS-DEF-157/SOS-BUG-923: Deleting spaces between words and re-adding them adds " " in Source (causing search to not return pertinent results in on-premises).
SOS-DEF-158/SOS-BUG-937: Filters do not save when date conditions use "is within the last" field.
SOS-DEF-159/SOS-BUG-956: Test Run "Execution Date" updates when users selects "Save and Close" but has not started the Test Run or made any edits.
SOS-DEF-184/SOS-BUG-722: Attachment file size is incorrectly obtained, resulting in lack of indexing/text extraction for Excel attachments.
SOS-DEF-189/SOS-BUG-878: Filters take a long time to load (>1 minute) if thousands exist in Jama instance.
SOS-DEF-203/SOS-BUG-640: Next button does not work in Chrome-IE for customers in specific Time Zones.
SOS-DEF-204/SOS-BUG-699: Emails containing ".-" are not accepted by Jama when creating a new user.
SOS-DEF-206/SOS-BUG-710: If a user selects a field mapping while importing a document into Jama, but doesn't have all the required fields of the mapping, Jama will scramble the mapped fields.
SOS-DEF-207/SOS-BUG-752: Items can be missing sequence number in SOAP getBaselines call if the item has a newer version than the version captured in the baseline.
SOS-DEF-209/SOS-BUG-776: getItemsForBaseline SOAP call does not return anything if the current version of an item is greater than the version captured in the baseline.
SOS-DEF-212/SOS-BUG-913: Relationship Import Plugin use does not create entry in Activities tab or event entry table.
SOS-DEF-216/SOS-BUG-636: User without "Manage Project" permissions cannot run custom Word template.
SOS-DEF-226/SOS-BUG-459: The activity stream does not return Deleted Item results if you search by document key (Unique ID).
SOS-DEF-227/SOS-BUG-508: Word Documents with Numbers in front of item names are deleted upon import.
SOS-DEF-240/SOS-BUG-626: Text within the Diagram Editor does not honor spacing.
SOS-DEF-246/SOS-BUG-382: Clear Synchronization Data dialog in legacy JIRA Connector doesn't express severity of action.
SOS-DEF-253/SOS-BUG-555: If an Admin edits a user's public filter, the author is changed to the Admin so it can no longer be edited by original author.
SOS-DEF-255/SOS-BUG-662: Users with only a reviewer license can be set as a review moderator.
SOS-DEF-257/SOS-BUG-694: System-required field "Name" can be marked as not required for an item type, causing Jama to freeze.
SOS-DEF-268/SOS-BUG-1016: Users with Collaborator licenses do not have a Cycle drop-down, so they have no way of viewing Test Cycle Details.
SOS-DEF-389/SOS-BUG-490: Moving a Label in the Diagram Editor is not precise.
SOS-DEF-522/SOS-BUG-541: After setting up Crowd authentication, SSO cannot be disabled.
SOS-DEF-572/SOS-BUG-1057: When new Users select the link from the "Your New Jama Account" email they see a blank web page if using IE11.
SOS-DEF-638/SOS-BUG-886: In the Test Run execution window, the number of Test Steps stops displaying at 99.
SOS-DEF-673/SOS-BUG-731: Text does not line wrap properly in Reading View.
SOS-DEF-773/SOS-BUG-639: Description fields do not properly filter out control characters, leading to an invalid XML exception when an item is retrieved via API.
SOS-DEF-774/SOS-BUG-954: CROWD assigns all imported users the greatest license type regardless of the number available.
SOS-DEF-794/SOS-BUG-356: Deletion of Test Plan or individual Test Run does not affect Test Case Status as it should.
SOS-DEF-795/SOS-BUG-638: Batch Transition Workflow for more than 2000 items on SQL Server throws cryptic SQL error.
SOS-DEF-807/SOS-BUG-1078: Text Field in single item view in-line edit allows for input of more than 255 characters. The input now honors the 255 character limit. 
SOS-DEF-810: Users are unable to Restore deleted Test Plans.
SOS-DEF-950: Images inserted into the Diagram Editor do not show when saved.



#releasenotes
40 comments
6628 views

Comments

6 days ago

As of this morning, 8.25 is available in your Replicated admin console.

03-29-2017 14:10

As of this morning Jama 8.14 is now available in the Standard (and Airgap) channel.

12-01-2016 19:16

In case anyone is following this thread, I wanted to note that Jama 8.10.1 is now available on the Standard channel.

10-05-2016 19:05

That's in Steve's ballpark, so I'll give him time to respond. I think the plan is to create announcements in the REST API section when there are new public endpoints. For my part, I'll make sure to bring this up when I see it in release planning.

10-05-2016 18:55

Hi Kristina,

This is somewhat related to Ryan's earlier question:  where would one find the details of per-release changes to Jama (REST, SOAP) APIs? 
Full disclosure: I have the same question out to Steve in the REST category.

Thanks,
Mike

08-08-2016 22:16

Hi Kyoko,

Thank you for pointing this out. We are updating our help docs and getting a temporary community post written up to include these undocumented ports in the meantime. Sorry you had to run into this issue.

08-05-2016 22:34

The 8.4.1 system is finally up.  I had to open port 9879.
Also ports 9870 - 9880 need to be opened because they are used by Replicated for internal communication.

08-04-2016 22:18

Nick—thank you for helping Kyoko work through this issue!

Kyoko, I just wanted to confirm that the user guide is accurate, however, Replicated had updated between the publishing of the user guide and when you downloaded Jama. We need to work with them on communication.

08-03-2016 22:47

ah sorry we are CENTOS7. try this for ubuntu. /etc/default/docker

08-03-2016 22:39

Nick,
Thank you for giving me a direction.  Somehow, my Ubuntu does not have a folder docker.service.d... I will do some more investigation.

08-03-2016 20:06

Yes we got it working. We had to modify the docker http_proxy configuration file first because our servers are in a secure DMZ location and need a http proxy to get out on the internet. We found that if we did not modify the docker file we were unable to get the proper images of replicated and we ended up in the situation your in . Either no data under cluster or an AddNode button that would not work.

You can try this:
sudo systemctl stop replicated replicated-ui replicated-operator
modify /etc/systemd/system/docker.service.d/http_proxy.conf and append to the env line "NO_PROXY=localhost,127.0.0.1,localaddress,.yourdomain,localip"
sudo systemctl daemon-reload
reboot server
replace .yourdomainwith your company domain like .intel.com for us and localip use ip of server like 192.168.0.10 or whatever you have configured for your server.

run jama curl command again curl -sSL https://get.jamasoftware.com/docker | sudo bash -s no-auto

08-03-2016 20:01

Nick,

That's exactly the situation I have. This is a test server and I do not have any node under the Cluster tab.  I issued curl command, but still no node is added.  I am waiting for the reply from Jama support.
Were you able to make the 8.4.1 work?

08-03-2016 19:54

I do not work for Jama but ran into many upgrade issues as well with 8.4.1. Do you have any nodes in the cluster screen? do you have a button that says Add Node? If you have the Add Node button it will generate a script to run that should add the missing node for you. If you don't have the add node button it may be related to an outdated version of the replicated docker image. Try running the Jama install curl command again to pull down the latest replicated image. Is this a test server or production? If production please wait for Jama offical response in your support ticket. If this is a system for testing you can try these at your own risk.

08-03-2016 18:38

Is there any separated user guide for 8.4.1?

I installed 8.1.0 couple days ago, and the system was up.  However, Jama does not start anymore after I migrated to 8.4.1 dues to node setting.(I already open the support ticket yesterday, but the issue is not resolved yet).

I tried to find some information myself, but I cannot find any.  Contents in help.jamasofware.com cannot be for 8.4.1 because screen shots for Admin Console have "Hosts" tab which does not exist anymore in 8.4.1...it changed to "Cluster" tab.

07-28-2016 15:17

Yeah, I know what you mean. And I agree that it can be problematic to roll up the features in one big "this is the new feature announcement!" rather than publicize incremental progress. My hope is that we don't go this route again...but sometimes these things are a surprise to me, too.

07-27-2016 19:49

Thanks, Kristina. While I agree wholeheartedly with making Jama easier for end-users, I hope it isn't at the expense of super-users (who are often the ones crafting reports and scripted queries for rollup of data analytics for the upper management that pays for Jama :)

In the end, I just want to ensure I understand the Search bar's features and limitations, so that I can recommend to my users when to use it, and when to use a UI filter.

07-26-2016 17:58

Ryan, I think the intended way to build those sorts of queries is via filter, not via the search bar. I would say that the strategic vision of Jama is to have it be more adoptable by end-users, not super-users constructing Lucene queries. This is why we have the "quick filters" available with facets to search various fields—we want search to be faster and easier on an enterprise level.

As far as number two goes, I hear you on that. If you want to talk about it further, send me an email and we can set up a phone call.

07-26-2016 15:26

Thanks.

1. So assume I have a field ("Compliance", field name "req_compliance") which uses a picklist, and some of the picklist values include "Compliant", "Not Compliant" and "Partially Compliant". If I only want to return the "Compliant" values and omit the other two, what's the easiest way with the Search field?

Based on your explanation, I'm currently doing:

   req_compliance:"Compliant" AND NOT "Not" AND NOT "Partially"

Which initially seems to work, but is there a more effective way?

2. Hmm; this could make things a bit complicated for us. Since we don't necessarily upgrade to every Jama release which comes out (occasionally "skipping" releases due to bugs and such), when we *do* upgrade, we produce internal release notes for our own users, adding local colour (sic) for the changes in the new release which we know our users may be concerned with.

If we can't accurately determine exactly which Jama release a change or new feature went in to, it makes it difficult for us to prepare an accurate list of changes for our users.

07-25-2016 22:56

1. Lowercased boolean operators used to be treated as actual search terms, and now they are ignored. So if searched for ham and eggs, you would get results for ham, for eggs, and for and—so your results would be terribly bloated.

2. I think this was a change that was implemented before 8.1. We actually did a lot of behind-the-scenes search work and didn't announce it all until mid-2015 for our hosted environment. Because 2015.2-2015.5 were supposed to be performance and bug releases, not feature releases, no search work was announced.

Does that help? 

07-25-2016 20:28

Could someone provide an example use case of two of the particular search improvements mentioned in the 8.1 release notes above? I just want to ensure I understand them.
  • Search results will no longer contain items only containing the Boolean operators AND, OR, NOT (i.e. lowercased "and," "or" and "not" will be ignored).
Not sure I understand the wording of this one, so a use case would be great.
  • Search custom fields: previously, Jama custom field search would only include results from custom text fields. This will allow users to quickly find the information they are looking for.
What's meant by "custom field search" here? Is this the Search box in the upper right of the UI, or something else? I ask because in 2015.5, I can use the UI Search box to find custom fields of type "Integer" (e.g. plm_priority:45), and I get the results I expect. What exactly is supposed to have been improved in 8.1?

Thanks.

    07-25-2016 15:14

    Paul,
    Jama 8 cannot be installed as it was in the past. For more info on installing 8, here's a primer. We have an airgap installation available if you have concerns about network access.

    07-24-2016 18:02

    Can JAMA 2015.5 be upgraded to JAMA 8.x without the use of Docker? Can JAMA 8.x be downloaded as it has in the past as a .tar.gz to install as we see fit?

    07-19-2016 21:16

    We have released a hotfix for version 8.4 to the Standard on-premises channel. If you have 8.4 installed, you will need to upgrade to 8.4.1 to receive full support.

    07-18-2016 23:08

    Nick, thanks for working with the team on this through a ticket. I'll have to update the thread when the conclusion is reached, in case anyone else has the same issue.

    07-18-2016 20:03

    Is there anyway to install Jama 8.1 still? Our 8.4 upgrade failed and we are trying to roll back to 8.1 but running into reinstall issues.

    07-15-2016 21:11

    Ah -- thanks, Kristina. It didn't occur to me that I might be looking my my browser cache. When I do a full refresh, you're right, I now see that layout as expected.

    Thanks.

    07-14-2016 23:22

    Just a note in case anyone didn't get the email from our Marketing department: as of yesterday, Jama 8.4 is now available in the standard channel.

    07-13-2016 22:51

    Iris has been hard at work on the user guide between 8.1 and 8.4. There are new sections in 8.4 locally. You might have to clear your cache to get it to show up on help.jamasoftware.com. Here's a link to the section if you visit help: http://help.jamasoftware.com/migration_from_replicated_1_x_.htm

     

    07-13-2016 20:37

    In the 8.4 release notes, is the path to the User Guide's replicated.com upgrade instructions correct? I don't see a section of the User Guide entitled "Server Administration", either at help.jamasoftware.com, or in the included help of my on-premises 8.1 version.

    06-15-2016 16:25

    Yay! I'm interested to hear how the process goes for you since you've had so much experience with Jama.  It's much different than before (I'm still working my way through it...).

    06-15-2016 07:59

    Yes, I have got a license key, now. We will try to get it running... ;-)

    Thank you!

    06-14-2016 16:04

    I think that is misleading—the Standard version is now available, so you shouldn't be waiting on a download. I need to look into that email you got.

    The follow-up from Gustavo is what you need, but I have to admit the crucial info is buried in there. There is no longer a download file. See page http://help.jamasoftware.com/installation_of_the_admin_cons.htm for how you get Replicated, which will enable the Jama download. The other important thing you should have received is a license key. Did you get anything emailed to you with a .rli?

    06-14-2016 13:18

    Kristina,
    I have got an email directly after submitting the "download" request:
    Thank you for requesting the latest on-premises download of Jama. You have opted to use our standard delivery channel, which will be available for download in the coming weeks. When the download is available, you will receive a notification email. There is no additional action required at this time. 

    Additionally, I have got a follow-up email from Gustavo with some informational stuff. But I haven't found a link where I can download the necessary files...

    Have I missed something? I sent an email to Gustavo as well.

    Cheers,
    Sebastian

    06-09-2016 16:22

    Account owners are supposed to be following up, as it became available at the end of May. I saw you just submitted a download request—have you heard anything?

    06-09-2016 07:28

    I have requested a download for the standard channel and got an email that it will take a few weeks before it is available. When will it be available?

    Cheers,
    Sebastian

    05-31-2016 21:07

    Yeah, I don't think the 4k max is hit very often. It looks like when we initially filed the bug, it was because the customer inserted XML into the test case steps.

    05-31-2016 20:50

    This looks like an excellent release. Looking forward to it

    05-31-2016 20:35

    I guess this can be easily achieved by an url encoded picture.

    05-31-2016 20:25

    I'm looking at SOS-BUG-884 and can't imagine why anyone would or could have 4000 characters in a test case step; is that number correct?

    05-31-2016 19:40

    With new deployment to 8.0/8.1 Will there be an updated user manual coming soon? Thanks  Kimberly