Standard channel (Self-Hosted) Release Notes

By Kristina posted 04-26-2016 21:14

  
See this article for more information: Full Support and Best Effort Support Defined.

Note:
Versions of Jama which house EOL features naturally lose subject matter experts over time, Best Effort Support will have fewer suggestions or solutions in these cases. 


top of page

Jama Connect 8.49 Standard

Release date AU/US/EMEA: 2020/05/06

Baselines: Improved usability, organization structure and search

 

Baseline IDs

All baselines now display a unique and non-editable identifier that is generated when the baseline is created. 

Track baseline name changes

Previously, when a baseline name was edited it would update all activities with the new name, making it hard to track name changes in the activity stream. Now you can tell when the name of a baseline has been changed because the baseline ID stays the same and the name is updated. 

Updated the language from baseline folder to baseline source

Baselines have been previously grouped in source folders with other baselines that are made up of the same items. (For example, baselines created from a set of items, and from a review of the same set of items would appear in the same source folder.) "Source folders" are now called "Sources." They now have a green barrel-shaped icon to distinguish them and their unique behavior from folders.

 

Organizing the baseline tree 

Organization and project administrators now have the flexibility to organize their baseline tree using folders and drag and drop

 

Create, edit, and delete baseline folders

  • Create a folder at the root level:
    • From the Add drop-down menu, select Add Folder.  
  • Right-click on the folder, select Add Folder.
  • Rename a folder: right-click on the folder and select Edit

       Note: Only empty folders can be deleted. 
 

Edit the name of a baseline source

  • Right-click on the baseline source and select Edit source.

Drag and drop baseline sources and folders 

  • Move baseline sources from one location in the tree to another, from the root level to a folder, and between folders. 
  • Re-order baseline folders at the root level or inside a folder. 

You can't edit a baseline that has been signed, whether manually or in a review. 

  

The option to add a baseline is now limited to the source and the available options and language are simpler.

Before:
After:
Add and edit baseline modal language changes
  • Changed 'Baseline name' to 'Baseline'
  • Changed 'Baseline description' to 'Description'

 

Restore a deleted baseline

A project administrator can now restore a single baseline, or group of baselines from the same source, by selecting Restore in the activity stream. 

Restored baselines appear in their original location and are highlighted in blue. Restoration activity is also logged in the activity stream at both the project level and inside baselines. 

If a deleted source is restored it will be placed at the top of the baseline tree.
 

Undo baseline deletion 

Users that may have accidentally deleted a baseline can also quickly undo the deletion by selecting Undo in the confirmation message. 

New activity for baselines created from a review

An activity will be shown in the project and on the baseline when it was created from a review. The activity will include a link to the baseline.

 

New signature identifier in baselines

  • Baselines that have signatures have a new icon in the baseline explorer, making it easier to identify which baselines/reviews have one or more signatures applied.
  • Baselines with a signature can no longer be deleted. The signatures must be revoked first.
  • If the source for a baseline has been deleted from the project, users trying to create a new baseline or review from the baseline explorer will receive a message explaining that the source has been deleted. 

 

Baseline search and usability improvements

Use the new baseline search feature to find a source or baseline. Keep the number of project baselines and sources under 14,000 to maintain efficient search performance. 

When you type a search request, the results are highlighted so you can find them easily. 

 

When you clear the search field, the results from the previous search are expanded and highlighted in the baseline tree. 

When you create a folder or baseline, it is highlighted in the baseline tree. Selecting the baseline ID in the activity stream highlights the baseline and expands the source. 

 

Baseline permission updates

Users with write permission to a project, will now be able to:

  • create new baselines
  • delete, edit or restore baselines they created

Project administrators will continue to have the ability to manage any baseline in the project.  

  

Review Center:  Filtering, usability, and auditability improvements
 

Usability improvements 

This release introduces changes to the Review Center header, which offers streamlined workflows and improved usability.

  1. Review participants now see their individual status in the header, instead of the bottom left corner of the Filter/TOC panel. A public user's status, "In Progress" or "Finished" no longer appears in the review header.

  2. Views are now consolidated into a single drop-down menu: 

    • Review

    • Compare

    • Stats

    • Feedback

  3. For Approvers and Reviewers, the "Finish" button now appears in the top right next to the Actions menu instead of the Filter/TOC panel. Since this is the primary way to finish a review, we removed the option to finish the review from the Actions menu. Participants can still finish a review by reviewing and approving all items in the review, and clicking the "Finish Review" button in the blue bar.
  4. For Moderators with dual responsibilities, the review role toggle is now displayed in the header instead of the bottom left corner of the Filter/TOC panel.

  5. Changes to the style of the progress bar, highlighting toggle, and View drop-down menu creates a more consistent experience with the rest of Jama Connect. 

 

Filtering improvements in reviews

This release introduces a new filter-and-find experience for reviewers.  

From the review header, select Filter to open the filter panel, which now slides out from the left.

 

When you select filters, the active filters appear in a bar under the review header. 

Updates to filters 

When you select multiple filters, the workflow is the same as other areas of Jama Connect with multi-select filters.  

New filters allow moderators and power users to take action on the items that matter most—items that are potentially holding up review progress:

  • Items with open comments
  • Items with closed comments
  • Items with comments in a specific version
  • Items with comments by a specific participant

When filters are selected:

  • The number of items that match the filter criteria update dynamically. 
  • A subsequent find search can be performed based off the filtered items. 
  • Reviewers can navigate to different areas of the review workspace without losing their filter or search selection. For example, if you make a filter selection and go to another view, your filter selection is saved when you navigate back to the review. 

Note: Filtering does not persist across user sessions or browser refreshes. 

 

The Search/TOC tab that was part of the filter panel is now called Find. The default for this panel is the table of contents. 

 

 

When you select an item from the search results or table of contents, the item is selected and outlined in blue.

  • Previously, the highlight appeared only briefly, making it difficult to track the results. 
  • The outline goes away when you click outside it.
  • You can now scroll without the outline disappearing.

Highlighting improvements in reviews

The highlighting library in reviews has been replaced with a new library that provides more flexibility for future development.

Existing workflows for highlighting have been maintained with these exceptions:  

  • When highlighting is disabled, the reviewer can't highlight content in the review reading view. Previously, a reviewer could make highlights but they disappeared after saving the comment.
  • When highlighting is enabled, the reviewer can see highlights specific to the revision that is selected in the review header.  
 
Highlighting workflow and navigation tips

A reviewer can now:

  • Use the tab key to move between highlighted items.
  • Open the Comments modal for the highlight by pressing Enter or the space bar.
  • Close the Comments modal by pressing Escape.

Important: Creating reviews from a project now opens in a new browser tab. By default, most browsers block a new tab from opening so update your browser settings accordingly. 

Additional colors were added to improve the readability of highlighted content. These colors replace the previous library, which included one highlight color and red text. A darker shade of yellow appears when a reviewer hovers or tabs between highlighted items or overlapping highlights. 

 

Audit history available within the review

A record of important review activities is now available in a new tab under Stats. Creation date, version updates and changes to moderators are now easily accessible.

Activities included:

  • Review creation
  • Publishing a new revision
  • Review close — both manual and when a review automatically closes at the deadline date and time
  • Review reopen
  • Review archived
  • Review deleted
  • Review marked as approved
  • Electronic signatures being applied as part of approving a review with electronic signatures enabled in the review settings
  • Signature revoked

Signature activities will also display the signer role, if configured in the review settings.

Reviews with electronic signatures can no longer be deleted

Due to feedback from our users, reviews with electronic signatures can no longer be deleted. Reviews with signatures can still be archived.

In a review, when a moderator tries to select Actions > Delete review, they will see that the review cannot be deleted when an electronic signature is active. 

Under Reviews > Table view, moderators and review administrators will also see that the button to delete reviews has been disabled when a review has an active electronic signature.

EXCEPTION: This does not apply to project deletion. When administrators delete an entire project, the reviews associated with that project will also be deleted, even if they have an electronic signature.

  

Improved review organization and reporting

More clarity in review statistics

In a review, select Review > Stats to see three separate tabs of information:

  • Participant progress for this version
  • Item progress for this version
  • Review activity across versions

Under the newly refreshed Item progress tab you can see:

  • total items
  • item types contained
  • average time spent
  • version with start and end date
  • approval status chart


Export review audit history

Under the Review activity tab, you can now select Export to download a document that meets the FDA requirement for "generating accurate and complete copies of records in both human readable and electronic format suitable for inspection, review, and copying by the agency."

 

Sample output:  

Electronic signatures updates

Sign with your company's SSO

We are excited to announce that customers using SSO/SAML now have the ability to electronically sign reviews and baselines. You do not need to make any administrative changes or have your IT apply any updates.

Create or pick an existing baseline in any project, click on the Add signature option and complete the sign in request. After successfully signing the baseline, you can revoke your signature and delete the baseline. Please reference the user guide for details.

Note: The application is required to open a new window with your company's sign in screen. If you are attempting to sign electronically and you do not see this window, disable your browser's pop-up blocker.

 

Signature details now visible when finalizing a review

When electronic signatures are configured for reviews, users will see recently introduced signature meaning and signer role (if applicable) when finalizing a review.

If the organization utilizes SSO for authentication, the Approve and sign button will trigger the your company's sign in window to re-authenticate in order to apply an electronic signature.

As part of these improvements, we've streamlined the error messages to the user, removed buttons that should not be available for certain use cases and added links to the user guide for more information.

 

Review Export

Users are now able to export directly from a review to PDF or MS Word. The review export is configured to include a title page, participants section (which includes electronic signature information if applicable), the items included in the review and the item comments.

 

Additional clarity in review stats page

Multiple changes have been made to the Participant Progress tab contained in the review center Stats page in 8.45.

Users will now see:

  • Participant details that include moderator(s) of the review, an option to email the moderator(s), approvers or all participants directly, participant counts, the voting subject (if applicable) and the revision start and end date.
  • Approver status and reviewer status charts will now be displayed in bar graphs versus pie charts.
  • Status by review participant will be displayed in one table that contains all of the approval information, electronic signatures and participant progress in the review. The previous version had two tables that the user had to toggle to see all of this information.

 

New comment chart in reviews

Open comments by comment type can now be seen from the Review Center Stats Item Progress tab:

 

REST API Updates

Swagger default changed from 'latest' to 'v1'

  

In preparation for future REST API version work, Jama's Swagger has updated it's default REST version from 'latest' to 'v1'.
Use of named revisions such as 'v1' ensure that development teams retain control of version use as new versions are released, where "latest' is a rolling version which requires complex development solutions.

How does this impact developers:
A change of default in Swagger will not change the way your current API Calls will function, it simply presents a more sustainable revision to first time users of Jama's REST API.
Developers may still manually add 'latest' to the Swagger endpoint in order to test calls and generate Curl requests.
 

New API endpoints: Retrieve relationship rule sets

We have added the ability for API GET requests to supply Relationship Rule Sets to assist with integration processes.

Restored and enhanced GET / filter endpoint

Fixes a breaking change (SOS-DEF-2748) where private filters became hidden by default.

  • Private filters of the authenticated user will be included in the result set as expected.
  • Adds an optional parameter to dictate Public only, Private only, or both. (enhancement)
  • There are NO CHANGES to result schema.

 

API version sunset announcement

The release of Jama Connect 8.44 marks the beginning of a sunset period for the REST endpoint '/latest'.

Originally, when a new version was released, the /latest endpoint would cycle the architecture underneath to the most recent version publicly available. This way developers would not have to keep updating the version. However, an organization that was not prepared for this might experience breaking changes. To remove this risk, the /latest endpoint is being removed and replaced with unique named/numbered revisions going forward. 

Notes:

  • With this release, no new features or bug fixes will be released to /latest (though we will still correct breaking change behavior).
  • Beginning 05/22/2020, all tools connected to /latest are at risk of version removal and service outage. (This date may vary slightly.)
  • There are more details on the Jama Community.

Impact on Jama Connect users and Integrators:

  • Since this is a proactive change, and versions /latest and /v1 share the same schema, a simple search and replace in any integrations, code or properties, should bring you up to date.
  • All integrations and scripts that use the /latest endpoint will be impacted.
  • These changes will not happen automatically and require end user interaction.

Sample migration change:

A call to Jama asking for all items in sample project 57 would change
From https://product.jamacloud.com/rest/latest/items?project=57
To https://product.jamacloud.com/rest/v1/items?project=57

Updates from customer feedback

We received a lot of positive feedback following the addition of links to baselines and reviews within an item's version history and some suggestions to help with usability.

  • Single item view's version widget will show baseline/reviews in the order they were created (newest to oldest).
 
  • If a review has been deleted, the link in single item view's version widget will become disabled.
  • When a user creates a review from a baseline, the Review Wizard will open in a new browser window. This will ensure the user will not lose where they were working before being taken to Reviews. 
  • Exports can now be created in PDF format.  
  • Tooltips in the Explorer Tree now show the name of the item, rather than the item type. 
  • Filter logic has a "NONE" option in addition to applying "ALL" and "ANY" of the filter conditions to create the results set. 
  • The options to Delete in Risk Management Center have been changed to "Delete rows" and "Delete analysis" to avoid confusion for Moderators and Risk Administrators. When a Moderator goes to delete a risk analysis, the focus is placed on the cancel button versus the delete confirmation to avoid inadvertent deletion of an analysis. 
  • Velocity reports now include a stack trace for faulty code, which improves troubleshooting when you build reports.
  • Tags are now visible in List View. Note that they are not exportable.
  • When you relate items, container items in the Explorer Tree (sets, components) are displayed as gray icons when all items within aren't relatable.  
 
  • When you click Refresh Explorer, the Explorer Tree now maintains expanded components, sets, and folders. 
  • When viewing the Test Runs in a cycle table, the Test Case column now shows the ID in front of the name.
 
  • Admin tables, including the item type table, now have alternating row colors for improved readability.
  • When you hover over an item's icon in the Explorer Tree, the item's type and full name are now displayed. 
    This release adds the option to include images in the Test Run results column during test execution. 
  • This release adds the ability to create a Trace View from the list generated by selecting "#downstream" or "#upstream" links.

1. Following the relationship could link to a filter for either upstream or downstream items. 

2. Click the Trace View button to generate a Trace View from that filtered list. 

  • This release adds the option to restore deleted Test Cycles from the Activity Stream.
 
  • Added type-ahead search to single and multi-select fields in Single Item View. 
  • For test cases with images included in the test steps, images can now expand to a lightbox view.  
  • Updated the signature meaning for electronic signatures from "I approve this review" to "I approve the content of this review."
  • A reviewer can now transition to the compare view from V1 of a review with multiple revisions. No changes to the behavior of the compare view have been made—the compare view always loads the most recent revision compared to the next previous revision.

 

Additional updates and enhancements

 

Improved Trace View item detail

The right panel in Trace View shows readability improvements.

Consistent editing of items

The pop-up modal that appears after clicking the Edit button was removed to align with inline editing options (double-clicking or selecting the pencil icon). 

Consistency updates to license usage chart

The chart displaying float creator use within the administration module has been updated to address errors in the display of dates and adjusted to show content in UTC to remove confusion when comparing usage across time zones. The times indicate UTC and the user's offset to UTC is indicated in the description below the chart.

Risk usability improvements

When a risk administrator removes all fields from a section in a risk template, the section header and risk analyses no longer appear in that template. Also, the section itself is no longer visible to users when they view definitions in the risk analysis. 

Note: The Adjust Rankings section is an exception to this rule. If you enable a ranking field before mitigation, the section is still displayed. 

 

Jama Connect User Guide improvements

Thumbnail and lightbox images

Applying the thumbnail and lightbox feature to images reduces the impact of many large images so you can focus on the content. We've applied this option throughout the guide, particularly in topics with a lot of screenshots or when the screenshot is tucked inside a note. Select the image to enlarge it. 

 

Updates to permissions presentation

Differences between User Roles and Access Permissions have been clarified. 

Content within documents over 25MB will no longer be searchable

Historically, documents' contents have been included in the search index data regardless of file size. To increase efficiency of indexing processes, this previously unbounded size limit has received a size cap of 25MB. Jama will continue to accept files of any size as attachments and description text and names of the attachments will continue to be searchable.

Content within a ZIP or similar archive will continue to be omitted from the search.

 

Velocity reporting update

A new Velocity reporting feature is now on by default and available to all users. For more information, see Velocity Reporting Usage FAQ

  • A new proxy is inserted between Velocity reports and the database, making the connection more secure. Only methods known to be in use will be included in the proxy. Methods and sub-functions which perform or allow database-level modification are excluded from the proxy.
  • Velocity reports are simplified, making the creation of new reports easier.
  • New proxies or changes to the released proxies will be reviewed on a case by case basis for inclusion in future updates to the Jama Connect service.
  • In the Velocity documentation, the previous error when searching for classes has been fixed.

 

Notes for on-premises administrators

Container artifacts

  • Replicated release number: 2.42.5
  • Java version (JDK_UPDATE): 11.0.6
  • NGINX_VERSION: 2.4
  • TOMCAT_VERSION: 8.5.50

 

Base URLs with double slashes

Due to recent security changes in Spring Framework, URLs with double slashes are no longer supported. In Jama Connect, the base URL setup in the root administrator account must not contain a trailing slash to prevent system URLs from containing double slashes. 

For example, instead of http://localhost:8080/contour/ with the trailing slash, the URL must be http://localhost:8080/contour. In most cases, Jama Connect is set up without a trailing slash. If, however, you have a custom base URL with a trailing slash, you must edit it to remove the trailing slash. You can change the base URL from the root administrator account. 

This issue will be addressed in future releases. 

Updates to administrator options

  • Self-hosted administrators can allow SVG images generated by the WIRIS equation editor, which uses scientific and mathematical symbols.
  • Anonymized usage data collection is now enabled by default for on-premise installations. For more information, see Usage Data FAQ

 

Search Services

This release upgrades Search Services. 

 

New default memory settings

This release introduces changes to the default memory settings.  Review your current memory settings. If using default settings, you don't need to make any changes. 

For details, see Configure memory settings in the Jama Connect User Guide.

 

Update the docker host system

  1. Edit the /etc/sysctl.conf file: add vm.max_map_count=262144.

  2. Stop Jama Connect: replicatedctl app stop --attach.

  3. Stop the docker service: sudo systemctl stop docker. 

  4. Reload the sysctl.conf file: sysctl -p. 

  5. To confirm, type this command: sudo sysctl -a | grep max_map_count. The system responds with vm.max_map_count=262144.

  6. Start the docker service: sudo systemctl start docker.

  7. Start Jama Connect: replicatedctl app start.

 

Resolved issues

ID Resolution
SOS-DEF-450 Administration: License detail graph is showing incorrect date. (SOS-BUG-553)
SOS-DEF-713 Review Center Stats Report cuts off time in date section. (SOS-BUG-1088)
SOS-DEF-765 Editing date field (custom and pre-defined) is inconsistently saved when date format is changed to dd/mm/yyyy. (SOS-BUG-1069)
SOS-DEF-1340 In the review Single Item View, related items now successfully update when switching between items.
SOS-DEF-1447 Time zone is incorrect in Review deadline on Windows client for CEST customers.
SOS-DEF-1777 User can create multiple signatures by clicking multiple times in "Review Complete" window.
SOS-DEF-2264 In Reading or List View, relationship rules no longer break when using the "Relate to existing" action. 
SOS-DEF-2403 When publishing a new revision of a review, the related items checkboxes don't honor the settings you selected.
SOS-DEF-2475 Password change error received "Incomplete reply from the server" because of MS SafeLinks.
SOS-DEF-2537 When working in the Review Center, highlights no longer disappear when editing highlights text before publishing new revisions. 
SOS-DEF-2660 In some cases, an error appeared when accessing reviews. This release resolves this issue. 
SOS-DEF-2762 In Trace View, the configured label appears instead of the default label. 
SOS-DEF-4064 Logout timer is now working is now working as designed.
SOS-DEF-4202 When a baseline folder is created, a message now appears in the activity stream.
SOS-DEF-4256 Rest API now allows items to be related when “Allow relationships with item types not in this rule” is enabled and any combination of rules are set.
SOS-DEF-4436 Selecting a date in the reviews wizard calendar does not respect the dd/mm/yy format configured (e.g. EMEA customers see US date format, not what they configured).
SOS-DEF-4444 Links to reviews in the Single Item View versions widget are only active when the user is a moderator of the review.
SOS-DEF-4447 Chemistry editor icon is missing from the rich text editor.
SOS-DEF-4484 Reviews are closing prematurely
SOS-DEF-4509 Boolean parameters are not being populated when "Context Sensitive" is selected for Velocity reports.
SOS-DEF-4513 Velocity Report: getId() function for the Organization class is missing.
SOS-DEF-4523 The horizontal scroll bar is not present when expanding an image in an item description box.
SOS-DEF-4531 Security - XSS cross scripting issue
SOS-DEF-4534 SAML eSignature: unhelpful user message, needs clarity and direction to check for popup blocker
SOS-DEF-4548 Viewing comments or connected users results in HTTP Status 400 Bad request (Chrome v. 79 and MS Edge Chromium)
SOS-DEF-4557 List view filtering menus "view all" option only displaying a maximum of 10 results
SOS-DEF-4558 You can now delete date fields in an item using inline edit mode. 
SOS-DEF-4579 In some cases, upgrading Jama Connect 2015.x or earlier to Jama Connect 8.x caused dates to update without editing due to a UTC change. This release resolves this issue. 
SOS-DEF-4595 Word templates containing VBA macros now successfully export. 
SOS-DEF-4601 Exporting from Microsoft Word now correctly saves settings from the template. 
SOS-DEF-4603 In some cases, text entered in the rich text editor using full-screen mode wouldn't save when a session timed out. This release resolves this issue.  
SOS-DEF-4607 Row highlighting in Risk Management now highlights the entire row. 
SOS-DEF-4619 An error no longer appears when accessing a project if the dashboard's Activity Stream widget has "Baselines" selected in the Activity Filter settings.
SOS-DEF-4622 Upstream items are now correctly displayed as upstream relationships in the "All Item Details" report. 
SOS-DEF-4623 You can now successfully import relationships when migrating from IBM Rational DOORS.
SOS-DEF-4638 Exporting a review no longer includes deleted comments. 
SOS-DEF-4666 When using Google Chrome 79 and 80, Microsoft Internet Explorer and Edge browsers, the correct icons are now displayed in the Results column in the Test Run execution window. 
SOS-DEF-4680 You can now select multiple steps when executing a Test Run. 
SOS-DEF-4693 In some cases, closing a review produced a Minified React error #185 message. This release resolves this issue. 
SOS-DEF-4705 Replicated startup scripts no longer cause permissions to reset when a file is placed in the wrong location. 
SOS-DEF-4708 Creating a new baseline folder is no longer blocked by the "Add folder" pop-up window. 
SOS-DEF-4710 Relationship rules are recognized when adding the "Related item" relationship type to a project.  
SOS-DEF-4713 In some cases, deleted items didn't appear in reports because of permission checks. This release resolves this issue.

  

Known issues

  • If attempting to sign electronically using SAML authentication and your company's sign-in window doesn't appear, disable your browser's pop-up blocker.
  • In certain circumstances, some unicode special characters might not correctly generate when exported to PDF.
  • REST API: PUT /users/{userId}/active endpoint accepts null/negative/positive values and also activates and deactivates the user.


Jama Connect 8.42.3 Standard hotfix

Release date AU/US/EMEA: 2020/02/05

This patch release addresses an incompatibility with a recent Google Chrome update that can cause the comment feature to be unresponsive and reviews to close before the scheduled time. A cross-site scripting (XSS) issue is resolved, and customers accessing Jama Connect behind a proxy can now access the Compare View feature. 

Resolved issues

SOS-DEF-2748        Project GET /filters no longer return private filters for an authenticated user.
SOS-DEF-4346        Review Center calls to Jama Services now recognize the context path in an environment with a proxy. 
SOS-DEF-4484        Reviews now close at the scheduled time. 
SOS-DEF-4531        This release resolves a cross-site scripting (XSS) issue. 
SOS-DEF-4548        Using Chrome 79 or Microsoft's Edge Chromium to view the Stream and Comments section in a single issue view no longer causes an error. 

 

top of page

Jama Connect 8.42.1 Standard

Release date AU/US/EMEA: 2019/10/03

New capabilities

Reviews: Improved usability and compliance

The following feature requests and usability improvements will ensure compliance and efficiency when setting up a new review.

  • View related items: When defining your review and selecting content, you can choose to make related items visible.
    view related

  • Smarter default settings: All review settings have been moved to a single page. All reviews now default to public with electronic signatures enabled.
    smarter default

     
  • Easier and more compliant assignments: Participants now default to "approver" as their review role. With signer roles enabled, moderators can assign a specific capacity for an electronic signature, making electronic signatures more compliant with FDA 21 CFR Part 11. (Signer role names are derived from group names.)
    easier assignments

     
  • Dynamic notifications: The system now builds different email invitations that reflect individual participant's review and signer roles. Email also contains the default signature meaning "I approve this review."
    Dynamic notifications


Baselines improvements 

Baseline defaults to List View: By popular demand, the default view for a selected baseline has been changed to the list of baselined items. Select the home icon to access baseline details.

Baselines defaults to list view


Find all baselines and reviews for an item: 
You can now select Versions in the side toolbar to open the bottom panel and find links to all baselines and reviews for each version of an item. The review or baseline must still exist and, for reviews, users must have been invited to the review for the link to work. 

find all baselines and reviews for an item

Additional layer of signature protection added to baselines: When a review has been electronically signed, any review baselines that have been created from that review can no longer be deleted. 

 

Risk Management improvements

Traceability: Items provide visibility to linked risks across the application. In most views (excluding reviews and baselines), you can configure fields to add the risk field and see risk linked items in the context of Reading, List or Trace

View and their exports. Additionally, selecting the risk icon opens a side panel where you can see the analyses and the risk IDs where the item is linked. Select those links to navigate to the associated risk or analysis.

Risk Management Center traceablility
New single item view widget: When the Risk Management Center module is licensed, administrators will have the ability to include a risk widget that will show all risks linked to items.

single item widget 

Risk IDs: These IDs are now visible at the beginning of each row in a risk analysis. You cannot edit or customize risk IDs, but you can sort them in ascending or descending order by selecting the column header.

risk id

Risk/benefit analysis: With the added EVALUATE RISKS column, your team can add necessary notes about each risk during a risk/benefit analysis.
Risk Benefit Ana

Column resizing in risk analyses: Click and drag to adjust the column width in risk analyses to fit your data and improve readability.

column resizing


General usability improvements 

Single Item View uses top labels: New label positioning and capitalization provide space for field content, distinguish labels from content and resolve issues with labels wrapping mid-word.

 

More efficient user selection: The current user is now located at the top of the window for quicker selection.

efficient user

Improved image options in Rich Text Editor

  • When expanding an image to see it at full size, the system will now use a white background instead of black for better clarity.

  • Images larger than the browser window can be scrolled.
  • For on-premise customers, the file attachment whitelist will now be honored for the rich text editor. This means file types such as SVG can now be added according to your IT security policies.

 

REST API: Improved batch delete restoration

When performing batch deletes, the previous restoration process required "all or nothing" restorations. With the improved API, you can restore individual child items without having to restore the entire batch deletion.

Note: Restoration of a child item will necessarily restore its parent container. Also, this restore does not block future restoration of other child items. 

REST API non-breaking changes migrated from /labs to /v1 

Updated:

  • GET /activities - includes additional events and item type data 

Added:

  • POST /picklists
  • DELETE /picklists/{picklistId}
  • POST /projects/{projectId}/itemtypes/{itemTypeId}
  • DELETE /projects/{projectId}/itemtypes/{itemTypeId}
  • POST /itemtypes/
  • POST /itemtypes/{itemTypeId}/fields

 

Velocity Report changes

With 8.42 you can now access upcoming changes in the Velocity reporting process. To enhance security, remove risk with post-release report changes, and simplify the creation of new reports, we are releasing a new version of the Velocity engine.

This new Velocity:

  • Uses a series of proxy functions which create a contract against the service code.
  • Removes all functions which allow reports to write to the database as it circumvents any Jama Connect methods to protect client information.
  • Dramatically simplifies the Velocity objects making for smaller, and easier-to-write reports.
  • Ensures application updates do not unintentionally break custom reports.

The changes to Velocity are currently released as opt-in and must be turned on by a system administrator for Jama Connect on-premises instances. When active, any existing reports will be automatically modified in memory to minimize steps required for administrators.

Community Information and FAQ located: https://community.jamasoftware.com/blogs/kristina-king/2019/09/13/velocity-reporting-update-faq 

Permanent change for Self-Hosted (on-premises) are slated for 8.48 (2020 Spring release):

    • Changes will continue to be made to proxy items through 8.44.
    • We suggest clients send copies of active in-use Custom Velocity Reports for development overview and inclusion.
    • Any report functions un-proxied by 8.44 public release will be reviewed in normal cadence of service update, not as defects to the service.

Interface Summary 

Resolved Issues

SOS-DEF-318/SOS-BUG-520

URL field validation was updated to require http://www.domain.com format. 

SOS-DEF-378/MAIN-BUG-328/SOS-BUG-327

Text items can be related to regular items through the Explorer Tree, but not through search. 

SOS-DEF-488/SOS-BUG-542

Unable to resize the column farthest to the right in List View if all the columns fit within the browser window.

SOS-DEF-492

Style inconsistencies exist in rich text tables.

SOS-DEF-529/SOS-BUG-813

Review item fields are not in the correct order in Reading View or Single Item View. 

SOS-DEF-531/SOS-BUG-787

Item notification links change once new revision is published. 

SOS-DEF-602

Selecting Projects while in Admin does not display the last project in the list if you have 15+ projects/folders. (SOS-BUG-949)

SOS-DEF-620/SOS-BUG-605

In Admin > Collaboration settings, "Only allow emails with these email domains" doesn't allow domains with symbols such as "-" or "_". 

SOS-DEF-633/SOS-BUG-802

List View filter facet does not filter out results when exported. 

SOS-DEF-672/SOS-BUG-719

User can't scroll through item type drop down when using Actions > Convert to

SOS-DEF-955    

Sorting by project in the reviews table view does not sort alphabetically.

SOS-DEF-1148

Lookup fields are auto-populated, on item creation, even though no pick list option is set to "Default".

SOS-DEF-1584

Calculated fields are not re-calculated when a related item is updated.

SOS-DEF-1640

Comment count in List View does not update to reflect the correct count after a comment is deleted.

SOS-DEF-1656

User shouldn't be able to select Add baseline once modal is open.

SOS-DEF-1790

Update moderators is not available from the Actions menu in a review when "Let approvers add reviewers" is unchecked.

SOS-DEF-2034

Swagger does not work when customer is using reverse proxy, potentially affecting integrations.

SOS-DEF-2134

Custom fields of type URL give an "invalid URL" error if input contains ":" symbol.

SOS-DEF-2231

User is not notified when filter searches containing embedded filters reach top limit and search results are affected.

SOS-DEF-2250

Related items links are missing from a review after being converted to another item type.

SOS-DEF-2257

Tags with a name starting with "#" do not open when selected.

SOS-DEF-2313

Updating an item's URL field with REST API doesn't work unless the URL includes .com.

SOS-DEF-2407

Adding a comment with Enter key in Add Signature to Baselines or Reviews displays unwanted text in the comment.

SOS-DEF-2430

Creating a baseline from multiple individual items can break a review.

SOS-DEF-2687

User is able to create tag names in the REST API that exceed the maximum length limit.

SOS-DEF-2688

When entering an invalid request in GET for files in the REST API, validation status does not display.

SOS-DEF-2874

Calculated field adds values from related items that were deleted.

SOS-DEF-2986

Single Item View of reviews reformats various text options so that they don't match the item.

SOS-DEF-2992

Export from Trace View generated by a search with spaces returns empty results.

SOS-DEF-3022

Trace View filters misalign when right panel is extended toward the left side.

SOS-DEF-3068

Users with ø letter or umlauts in their first/last names will not be displayed correctly in the User Profile link.

SOS-DEF-3093

Pie chart value "Max Elements to Show" displays less one option that what's configured.

SOS-DEF-3992

Custom URL field requirements are more stringent on adding than on editing.

SOS-DEF-4072

System Health Report email links' destinations are incorrect.

SOS-DEF-4233

A filter that contains common characters after percent encoding (eg. %20) displays incorrect filter name in Trace View.

SOS-DEF-4263

Custom field Flag defaults to "False" on pre-existing items but the actual value is null.

SOS-DEF-4265

Bar charts on dashboard are not sorting in requested order, but rather by number of results.

SOS-DEF-4268

Expanding the Change project dialogue box results in empty white space in expanded area.

SOS-DEF-4294

Folder has "phantom" status when imported through the Data Import Wizard.

SOS-DEF-4308

User can enter too large of search string for adding links in Risk Management.

SOS-DEF-4365/SOS-DEF-530/SOS-BUG-1013

Single Item View's link widget does not show more than 20 links. 

 

Notes for self-hosted administrators
 

    • Note: Prior to upgrading or installing 8.42, there is a required step-upgrade to 8.36 first. When in the Replicated Admin Console, selecting Upgrade will install 8.36 first behind the scenes.
    • We regression tested using Replicated 2.38.1 and recommend the use of the following script for the initial installation of Jama Connect.  This will install Replicated 2.38.6, which is the same as 2.38.1 but with a security patch applied. curl -sSL "https://get.replicated.com/docker?replicated_tag=2.38.6&replicated_ui_tag=2.38.6&replicated_operator_tag=2.38.6" | sudo bash -s no-auto
  •  
    • Container artifacts
      • Replicated release number 2661
      • Java version (JDK_UPDATE): jdk-11.0.3+7
      • NGINX_VERSION:  1.16.1-1.el7.ngx

      • TOMCAT_VERSION: 8.5.42

        Airgap customers can download the necessary version of Replicated via https://s3.amazonaws.com/replicated-airgap-work/stable/replicated-2.38.6%2B2.38.6%2B2.38.6.tar.gz before installing the 8.42 Airgap file available in your portal. Please note, 8.36.0 is a required update and must be installed prior to upgrading to 8.42. The Replicated Admin Console will force this upgrade path, so you must download both Airgap files and place them in the upgrade directory.

 

top of page

Jama Connect 8.36.4 Standard Hotfix

Release date AU/US/EMEA: 2020/02/05

This patch release addresses a recent Google Chrome update that can cause the comment feature to be unresponsive. A cross-site scripting (XSS) issue is resolved, and customers accessing Jama Connect behind a proxy can now access the Compare View feature. 

Resolved issues

SOS-DEF-4346       Review Center calls to Jama Services now recognize the context path in an environment with a proxy. 
SOS-DEF-4531       This release resolves a cross-site scripting (XSS) issue. 
SOS-DEF-4548       Using Chrome 79 or Microsoft's Edge Chromium to view the Stream and Comments section in a single issue view no longer causes an error. 

top of page



Jama Connect 8.36.2 Standard Hotfix

Release date US/EMEA/AU: 2019/10/04 

Resolved issues

Updated NGINX version to1.16.1 to mitigate the August 2019 HTTP/2 Vulnerabilities.

https://www.nginx.com/blog/nginx-updates-mitigate-august-2019-http-2-vulnerabilities/ 

* NGINX is an open source application included with Jama Connect to aid with routing of traffic. 

top of page


Jama Connect 8.36.1 Standard

Release date US/EMEA/AU: 2019/07/03 

Resolved issues

SOS-DEF-2034: Reverse proxy may affect Swagger and integrations such as Tasktop and OpsHub.

AUD-DEF-206: Incorrect database table orderings in the export/import/backup.dtd causes imports to MS SQL to fail with a foreign key constraint violation.

Removed inconsistent validation of the custom URL field.

Customers reported difficulty with integrations and data entry into the custom URL due to inconsistent validation and limitation to the format of http://www.example.com.

Includes defects:

SOS-DEF-3992: Custom URL field requirements are more stringent on adding than on editing.

SOS-DEF-318: URL field validation was updated to require http://www.domain.com format. (SOS-BUG-520) 

SOS-DEF-2313: Updating an item's URL field using the REST API will not accept a change unless the URL includes .com.

top of page


Jama Connect 8.36 Standard

Release date self-hosted: 2019/04/16 US/EMEA/AU

Note: This release (8.36) will be a required step-upgrade for any Self-Hosted customer who wants to upgrade to any future versions of Jama Connect.

Risk Management Center is now available!

The 8.36 release marks the availability of Risk Management Center to our Self-Hosted customers. Risk Management Center comes with templates based on ISO 14971 and IEC 60812, allowing development teams to conduct risk analysis using Preliminary Hazard Analysis (PHA) and Failure Modes and Effects Analysis (FMEA) techniques.

Risk Management Center Home Page Capabilities

  • A user with risk administrator permissions can modify templates to adapt to your organization’s needs.

  • Bookmark analyses to keep important ones at the top of the list.

  • Filter analyses by user's role.

  • Risk analyses can be filtered by keyword to help users find the analysis they're looking for.

  • Users can page through their available analyses using the "Load more" functionality seen on the Jama Connect Home page. "Load more" works for both recently viewed risk analyses and bookmarked analyses.

  • Users can see an indication of risk analyses that are currently locked for editing by another user on the risk management home page.

Risk Analysis Capabilities

  • Risk moderators create an analysis from an ISO 14971 or FMEA template and invite participants.

    (ISO Example)

    (FMEA Example)

  • Add links to Jama Connect items to document risk control.

  • Add multiple links on all text fields.

  • The filter panel in the risk analysis allows users to view and focus their filter criteria.

  • Risk analysis and template names are editable inline, in order to be consistent with the editing experience in the Trace View.

  • Risk analyses can be exported to Excel.

Setting Page Capabilities

  • Customize risk value levels (numbers or text) for your risk analysis process.

  • Modify columns in the risk analysis template by changing the name, description, and allowing links.

  • Risk administrators can choose up to 12 options for a risk matrix.

Risk Management Center requires additional licensing for your organization, as well as creator, stakeholder or test runner licenses for all risk management participants. Contact your Jama Software account manager for more information. 

WIRIS MathType for Airgap/Self-hosted 

Self-hosted customers with a requirement to keep traffic inside their firewall can now get a MathType license that allows you to use MathType from a local MathType server.  This way users can enter math and chemistry equations in rich text fields, without calls or responses outside your protected environment.

Learn More Tab Update

The "Learn more" tab has been updated to provide links to helpful Jama Connect content.

Reading View Improvements

We have changed Reading View text sizes, styling, and spacing to bring 25-30% more content onto each screen. This improves readability and saves time, especially for those who write each requirement as a short statement instead of longer prose. 

Item Type Widgets Removed

The support has ended for item type widgets "Selenium" & "Test Results (legacy)" and you can no longer configure them. 

Resolved Issues

SOS-DEF-2494: GET /tags/{id}/items returns unexpected results.

SOS-DEF-2934: All notifications from Reviews fail to be generated for data sets with multiple organizations.

SOS-DEF-2990: Trace view relationships not displaying for users without explicit Read permissions.

SOS-DEF-764: In List View, inline editing a predefined date field does not save the value.

SOS-DEF-3044: Batch edits of multi-select fields will save different content than the user selected. 

SOS-DEF-1916: Editing a CKeditor field from List View removes content between angle brackets. 

SOS-DEF-2374: While inline editing in List View, when pressing enter, the cursor focus no longer steps down to the next row’s field on the same column. 

SOS-DEF-3099: Progress bar gets stuck for Word exports with images on newer Ubuntu versions via Velocity reports. 

SOS-DEF-3125: Keyboard input sometimes does not show up in the comment box when doing @mentions with IE11 and > ~1200 users. 

SOS-DEF-3143:  Relating multiple items at a time results in non-deterministic paginated sorting.

SOS-DEF-3991: REST API "GET Upstream/Downstream related items" has non-deterministic sort order. 

SOS-DEF-1068: Authentication: Crowd sync fails if a group and user in that group are deleted before the next crowd sync. 

SOS-DEF-1576: Review Center "Copy Link" is a different URL than just clicking on a review, leads to a "Oh no!" page. 

SOS-DEF-2521:  Crowd sync fails completely if there is at least one invalid user in the Crowd database.

SOS-DEF-2697: LDAP sync fails if any Jama accounts have associated LDAP entries without last name. 

SOS-DEF-403, MAIN-BUG-357, SOS-BUG-342:  Reviewer will receive an error when attempting to delete a comment of type Proposed Change in Review Center.

SOS-DEF-476, MAIN-BUG-145, SOS-BUG-249:  Data in Word export doesn't include fields that exist in downstream items if the field doesn't exist on the exported item.

SOS-DEF-635, SOS-BUG-847:  Unable to save a sub-item from created from an item that is locked by workflow.

SOS-DEF-1088:  Relationship status column not showing correct value in Dashboard and Coverage Explorer.

SOS-DEF-1201:  'Switch Direction' option from the Visual layout view of the Relationship widget does not work and user prompted with incorrect message: "You don't have permissions to perform this action".

SOS-DEF-1961:  Exporting Word templates in .docx format results in a .doc export.

SOS-DEF-2153:  Approvers who do not have read access to the project will receive an incorrect permissions error when approving any item that has an Item of Type field.

SOS-DEF-2340:  JMX (Java Monitoring) will not work for Elasticsearch and Diff services.

SOS-DEF-2469:  Mail Merge <> field on related items does not work when exporting from List/Reading View.

SOS-DEF-2524:  If the threshold of active creator licenses is reached, new users can't be added to Jama via Crowd sync.

SOS-DEF-2774:  Refresh button is not working from Review Center Stats view.

SOS-DEF-4069: The image "tool-sprites.gif" is not using the customers set context path, causing icons to not render.

 

Notes for self-hosted administrators

    • We regression tested using Replicated 2.32.2 and recommend the use of the following script for the initial installation of Jama. curl -sSL "https://get.replicated.com/docker?replicated_tag=2.32.2&replicated_ui_tag=2.32.2&replicated_operator_tag=2.32.2" | sudo bash -s no-auto
    • Container artifacts

 

top of page

Jama Connect 8.31.7 Standard Hotfix

Release date AU/US/EMEA: 2020/02/05

This patch release addresses a recent Google Chrome update that can cause the comment feature to be unresponsive. A cross-site scripting (XSS) issue is resolved, and customers accessing Jama Connect behind a proxy can now access the Compare View feature. 

Resolved issues

SOS-DEF-4346       Review Center calls to Jama Services now recognize the context path in an environment with a proxy. 
SOS-DEF-4531       This release resolves a cross-site scripting (XSS) issue. 
SOS-DEF-4548       Using Chrome 79 or Microsoft's Edge Chromium to view the Stream and Comments section in a single issue view no longer causes an error. 

top of page

 


Jama Connect 8.31.5 Standard hotfix

Release date US/EMEA/AU: 2019/10/04

Resolved issues

Updated NGINX version to1.16.1 to mitigate the August 2019 HTTP/2 Vulnerabilities. 

https://www.nginx.com/blog/nginx-updates-mitigate-august-2019-http-2-vulnerabilities/ 

* NGINX is an open source application included with Jama Connect to aid with routing of traffic.

 

top of page


Jama Connect 8.31.4 Standard

Release date US/EMEA/AU: 2019/07/03 

Resolved issues

SOS-DEF-2034: Reverse proxy may affect Swagger and integrations such as Tasktop and OpsHub. 

Removed inconsistent validation of the custom URL field. 

Customers reported difficulty with integrations and data entry into the custom URL due to inconsistent validation and limitation to the format of http://www.example.com. 

Includes defects:

SOS-DEF-3992: Custom URL field requirements are more stringent on adding than on editing.

SOS-DEF-318: URL field validation was updated to require http://www.domain.com format. (SOS-BUG-520) 

SOS-DEF-2313: Updating an item's URL field using the REST API will not accept a change unless the URL includes .com.

top of page


Jama Connect 8.31.3 Standard

Release date AU/US/EMEA: 2019/03/10 

Resolved Issues

SOS-DEF-4056: System report "Test Plan Summary" fails with error when exported to MS Word.

There is a known issue where BIRT reports that include charts will fail when attempting to open with MS Word due to a library dependency that is not compatible with recent Java updates. The reports are still accessible when viewed with the HTML option.

The embedded version of BIRT, which is the SQL reporting engine included in Jama Connect, requires a feature that was deprecated in Java 4 and was not included in the OpenJDK 8 delivered with Jama Connect 8.31.2. Jama Software supplied out-of-box reports have had a small update applied that will remove the Java dependency for BIRT.

Customers that have developed their own custom BIRT reports will need to make updates if their reports align with the described issue. Update the output format  from "SVG" to "PNG" within any .rptdesign file that creates a chart as part of the report.

<property name="outputFormat">SVG</property>

to

<property name="outputFormat">PNG</property>

top of page


Jama Connect 8.31.2 Standard

Release date self hosted: 2019/02/27 AU/US/EMEA

Improved security 

Annual security penetration evaluation completed

  • Focus primarily on removing potential cross scripting (XSS) vulnerabilities

Upgraded to OpenJDK from Oracle JDK

  • Required to remain in alignment with new Oracle licensing changes and continue receiving security updates
  • Regression testing showed all systems function as expected after this upgrade

Known Issue:

There is a known issue where BIRT reports that include charts will fail when attempting to open with MS Word due to a library that is not compatible with Java updates. The reports are still available to be viewed with the HTML option. A fix for this known issue will be available soon in an upcoming release (8.31.3).

Resolved issues

SOS-DEF-1068 Authentication: Crowd sync fails if a group and user in that group are deleted before the next crowd sync.
SOS-DEF-1089 If you have an unlimited license, users synched from Crowd are set to LicenseType: Inactive
SOS-DEF-2521 Integrations - Crowd: Crowd sync fails completely if there is at least one invalid user in the Crowd database
SOS-DEF-2697 LDAP sync fails if any Jama accounts have associated LDAP entries without last name

top of page


Jama Connect 8.31.1 Standard

Release date: 2018/10/26

Resolved issues

SOS-DEF-2994: Importing data from Excel with dates results in incorrect or inconsistent results 

 

Dates now import accurately from Excel when they are contained in cells formatted as dates.

 

Note: If you are importing dates in text formatted cells in Excel, they must be in exactly this format to import accurately: mm/dd/yyyy hh:mm:ss Z, where Z is the time zone difference (for example: -0800, +1000, +0700).

-------------

top of page


Jama Connect 8.31 Standard

Release date: 2018/10/17
The latest Standard version is available in your Replicated Admin console. 


NEW CAPABILITIES

SAML

Update 2018/11/07: SAML for self-hosted customers is now available. See this link for more information: FAQ.

Filter Trace View

Items often have multiple upstream or downstream relationships to other items of different item types. This can make analyzing relationships for context, completion, or correctness difficult.  You can now filter the items you see in Trace View by item type. This way you can better focus on the relationships you want to analyze.

Username and password required for electronic signatures

Jama Connect continues to help customers focused on achieving compliance with CRF Part 11. When leaving an electronic signature in reviews or baselines, users are now required to enter a username and password.

 

REST API improvements

  • Jama Connect GET /filters endpoint now has the ability to specify filter scope and projectID is optional.
  • Last Activity Date option to v1/filters/{id}/results endpoints now allow better filtering scope control.
  • JVK files now include REST.

Accessibility improvements

Navigation for keyboard editing in List View, Single Item View has been improved in both view and edit modes.

 

Security improvements

 Additional cross-scripting defects were repaired.

 

Resolved issues

SOS-DEF-1830: Filters with embedded filters on Global ID can display incorrect results.

SOS-DEF-1995: Using a filter with "Has Test Case" condition for Test Run item types returns 0 results.

SOS-DEF-2095: Exception occurs when an admin attempts to edit a user group they are included in.

SOS-DEF-2386: REST API call GET /baselines/{baselineId}/versioneditems/{itemId}/versionedrelationships is slow on larger data sets.

SOS-DEF-2440: Reuse and Sync feature may create duplicate relationships if workflow is enabled.

SOS-DEF-2780: There is an inconsistency in ordering between baseline list view and the baseline due to change in globalSortOrder, affecting report output.

SOS-DEF-2864: Jama UI may show user a Session Expired dialog, but a background HTTP GET call keeps the user session alive.

 

Notes for on-premises administrators

    • We regression tested using Replicated 2.25.2 and recommend the use of the following script for the initial installation of Jama. curl -sSL "https://get.replicated.com/docker?replicated_tag=2.25.2&replicated_ui_tag=2.25.2&replicated_operator_tag=2.25.2" | sudo bash -s no-auto
    • Container artifacts
top of page


Jama Connect 8.25.6 Standard

Release date US/EMEA/AU: 2019/07/03 

Resolved issues

SOS-DEF-2034: Reverse proxy may affect Swagger and integrations such as Tasktop and OpsHub. 

Removed inconsistent validation of the custom URL field.

Customers reported difficulty with integrations and data entry into the custom URL due to inconsistent validation and limitation to the format of http://www.example.com.

Includes defects:

SOS-DEF-3992: Custom URL field requirements are more stringent on adding than on editing.

SOS-DEF-318: URL field validation was updated to require http://www.domain.com format. (SOS-BUG-520) 

SOS-DEF-2313: Updating an item's URL field using the REST API will not accept a change unless the URL includes .com.

top of page


Jama Connect 8.25.5 Standard

Release date: 2019/03/10 AU/US/EMEA

Resolved Issues

SOS-DEF-4056: System report "Test Plan Summary" fails with error when exported to MS Word.

There is a known issue where BIRT reports that include charts will fail when attempting to open with MS Word due to a library dependency that is not compatible with recent Java updates. The reports are still accessible when viewed with the HTML option.

The embedded version of BIRT, which is the SQL reporting engine included in Jama Connect, requires a feature that was deprecated in Java 4 and was not included in the OpenJDK 8 delivered with Jama Connect 8.31.2. Jama Software supplied out-of-box reports have had a small update applied that will remove the Java dependency for BIRT.

Customers that have developed their own custom BIRT reports will need to make updates if their reports align with the described issue. Update the output format  from "SVG" to "PNG" within any .rptdesign file that creates a chart as part of the report.

<property name="outputFormat">SVG</property>

to

<property name="outputFormat">PNG</property>

top of page


Jama Connect 8.25.4 Standard

Release date standard: 20YY/02/27 AU/US/EMEA

Improved security 

Annual security penetration evaluation completed

      • Focus primarily on removing potential cross scripting (XSS) vulnerabilities

Upgraded to OpenJDK from Oracle JDK

        • Required to remain in alignment with new Oracle licensing changes and continue receiving security updates
        • Regression testing showed all systems function as expected after this upgrade

Known Issue:

There is a known issue where BIRT reports that include charts will fail when attempting to open with MS Word due to a library that is not compatible with Java updates. The reports are still available to be viewed with the HTML option. A fix for this known issue will be available soon in an upcoming release (8.25.5).

Resolved issues

SOS-DEF-1068 Authentication: Crowd sync fails if a group and user in that group are deleted before the next crowd sync.
SOS-DEF-1089 If you have an unlimited license, users synched from Crowd are set to LicenseType: Inactive
SOS-DEF-2521 Integrations - Crowd: Crowd sync fails completely if there is at least one invalid user in the Crowd database
SOS-DEF-2697 LDAP sync fails if any Jama accounts have associated LDAP entries without last name

top of page


Jama Connect 8.25.3 Standard

Release Date: 2018/07/16

Resolved Issues

SOS-DEF-2655: Exports/Reports: Custom text box (non-rich text) field for an item is not UTF-8 compatible for 8.25 after upgrade. Symptoms include seeing a ? instead of an ǘ.

 

For some on-premises installations, when upgrading to 8.25.x, the default setting for files may incorrectly inherit the underlying host's default locale of ASCII instead of UTF-8. The fix directly sets this value correctly.

Administrator notes

      1. To determine if you are affected, check the Docker container's locale setting. From the command line, determine the container ID by entering the command below sudo is optional. This value can also be found under the Cluster option of the Replicated Jama Connect admin console.


        sudo docker ps

      2. Copy the resulting Container ID for jamacore and insert that into the next command sudo is optional.


        sudo docker exec -it jamacore-container-id locale

      3. If you do not see "LANG=en_US.utf-8" then we recommend upgrading. A short term workaround that only requires a restart is to set this value in Java. In Replicated, navigate to: Advanced Startup Settings > Additional JVM options for core Jama application and add this line:

        -Dfile.encoding=UTF-8

        and restart the application.

top of page


Jama Connect 8.25.2 Standard

Release Date: 2018/06/15

Resolved Issues


SOS-DEF-2612: A project reindex does not remove existing items from the Elastic Search index, resulting in items that are indexed but inactive. 

top of page


Jama Connect 8.25.1 Standard

Release Date: 2018/06/01

Resolved Issues

SOS-DEF-2621: When installing the Replicated environment on a new application server as part of the upgrade, an error on startup database already exists occurs when pointed at a pre-8.25 dataset. This has been resolved.

top of page


Jama Connect 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

            • The browser's native spell check is now accessible: cmd or ctrl + right-click.
            • 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.
            The design has been updated. Reading View in both Projects and Reviews now share a similar look and feel, with consistent hierarchical cues and font sizes.



 

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.

SOS-DEF-2506: Full system index of large projects may miss items and require individual project re-index.

 

NOTES FOR ON-PREMISES ADMINISTRATORS

            • In order to upgrade Jama Connect, Replicated must be upgraded to version 2.13.2. 
            • For new installations, please use the following script for the initial installation of the 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] 

top of page


Jama Connect 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.

top of page


Jama Connect 8.20.1 Standard

Release Date: 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.

top of page


Jama Connect 8.20 Standard

Released with 8.20.1

        < /br>

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.

 

top of page


Jama Connect 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.



top of page


Jama Connect 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.

 

top of page


Jama Connect 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.

top of page


Jama Connect 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.
top of page


Jama Connect 8.14.1 Standard

Release Date: 2017/4/21

Build Date: 2017/4/20

Resolved Issues

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

top of page


Jama Connect 8.14 Standard

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.
top of page


Jama Connect 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.

top of page


Jama Connect 8.10.3 Standard

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. 

top of page


Jama Connect 8.10.2 Standard

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.

top of page


Jama Connect 8.10.1 Standard

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.

top of page

Jama Connect 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.


top of page

Jama Connect 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.

top of page

Jama Connect 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

 

top of page

Jama Connect 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.

top of page

#releasenotes
40 comments
9881 views

Comments

05-15-2018 08:50

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

03-29-2017 11:10

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

12-01-2016 16: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 16: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 15: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 19: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 19: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 19: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 19:47

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

08-03-2016 19: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 17: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 17: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 16: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 15: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 12: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 16: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 14: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 12: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 19: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 17: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 12: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 15: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 18: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 20: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 17: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 18: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 20: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 19: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 17: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 13: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 04:59

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

    Thank you!

    06-14-2016 13: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 10: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 13: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 04: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 18: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 17:50

    This looks like an excellent release. Looking forward to it

    05-31-2016 17:35

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

    05-31-2016 17: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 16:40

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