Jama Integration Hub (JIH) Release Notes

By Jama posted 06-13-2015 00:31

  

Jama Integration Hub (JIH) UPGRADE VERSION 4.12.11

Published: 2017/12/19 (Download Jama Integration Hub - Jama Software)

Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

Summary: This release contains fixes for Jira, HP, TFS, and VersionOne.

Fixes since JIH 4.12.2

General Fixes

  • The Export Proxy Associations wizard now validates the artifact schema of all of the exporting tasks, and lets the user refresh the task where the schema does not match.

Connector-Specific Fixes

Atlassian Jira

  • Fixed an issue where parsing Jira nFeed user fields that don’t have key field in response payload results in error
  • Fixed an issue where restricted epic links caused an error in the Jira connector.
  • Fixed an issue where Resolution was not being set by JIRA status transitions
  • Fixed an issue with the Jira connector that was causing the Sprint label to include the goal description when the Sprint field was read.

HPE ALM

  • Fixes an issue where the connector does not properly distinguish expired sessions from failed authentication, leading to errors instead of re-authentication.
  • Fixed an issue where comments synced using Single Value Memo Field comments handling displayed raw HTML.
  • Fixed an issue where an expired session, resulting in a “permission denied” response, wasn’t triggering re-authentication.

Microsoft Team Foundation Server

  • Fixed an issue where resources were not always properly released when connections were closed by the Microsoft TFS Connector.
  • Fixed an issue where creating an artifact would cause an error in TFS 2015 RTM.
  • Fixes an issue where a closed team collection on a team foundation server causes the connector not to be able to retrieve the list of projects (for any team collection).

VersionOne

  • Fixed an issue with the VersionOne connector where it was unable to support the VersionOne On-Demand Fall 2017 Update.



Jama Integration Hub (JIH) UPGRADE VERSION 4.12.2

Published: 2017/10/31 

Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

Summary: This release contains feature updates and fixes for JIRA, Jama, HP, CA Agile and TFS.

Features since JIH 4.11.15

Atlassian JIRA

  • JIRA connector has been renamed from “Atlassian JIRA” to “Atlassian JIRA”.
  • JIRA connector now supports single and multi group picker fields.

HPE ALM

  • Added a new search type that allows the user to scope by domain, project, type, and a supplied query string.

Jama

  • Support added for Jama Tags.
  • Users can now route by Jama Components.

Microsoft Team Foundation Server

  • Support added (read-only) for the following Git related fields in TFS:
    • Commit
    • Pull Request
    • Branch
    • Tag

 

Fixes since JIH 4.11.15

General Fixes

  • Fixed an issue where database errors may occur during certain connector upgrades.
  • Fixed issues when upgrading with JIRA repositories, occurring during the post installation steps.
  • Fixed an issue where invalid Task IDs and URLs were generated when upgrading to the latest Jira connector.
  • Fixed a bug where updates to the synchronization log database would erroneously output that 0 records had been updated, and added detailed diagnostic information to errors which occur during post installation database updated.
  • Added action to mark comments on selected tasks as synchronized, preventing existing comments from being synchronized in the future.
  • Fixed an issue where errors may occur when processing files in Tasktop Sync’s workspace.
  • Tasktop Sync informs users when refreshing schema from the task list fails.

Connector-Specific Fixes

Atlassian JIRA

  • Fixed Epic Link appearing as read-only when Epic issue type is renamed.
  • Fixed an issue with retrieving sprint labels containing an equal sign in the Jira connector.
  • Fixed an issue with retrieving options for closed issues.
  • Fixed a bug that caused an error while doing person mapping in Jira.
  • Fixed an issue with the rank field on the creation screen.
  • Fixed an issue where deleted users would cause failures.
  • Descriptions and comments having tables in Jira are now produced with improved accuracy. Previously some rich text constructs such as lists within table cells could produce tables that were incorrectly formatted.
  • Fixed an issue which would cause errors when processing rich text if there were new lines between square brackets.
  • Optimized change detection of Jira artifacts.

CA Agile Central (Rally)

  • Connector will now check for errors parsing payloads and throw a specific exception for the operation to be retried.
  • Fixed an issue where only the first 20 options were returned for single-selects.
  • Filtered out duplicate release options in the CA Agile connector.

HP Quality Center and ALM (Mylyn)

  • Fixed an issue where requirements aren’t checked-in successfully after updating.
  • Tasktop Dev now supports authenticating with HPE ALM 11.5 and newer using unicode credentials.

HPE ALM

  • Fixed an issue with error handling in the HPE ALM/QC connector.
  • Improved the error message when users are removed or unassigned from projects in HPE ALM Quality Center.
  • Fixed an issue in HPE ALM connector where operations were failing due to ‘Session does not exist’ error.
  • Fixed an issue where expired PingFederate authentication sessions are not properly detected.
  • Fixed an issue where an error would be thrown when retrieving attachments of an artifact.
  • Fixed an issue in HPE ALM where line break characters were being removed from text.
  • Improved the performance for listing options for the Subject field.
  • Fixed an issue where listing options for test folders would fail with an error about duplicate results.
  • Fixed an issue where missing dependencies would cause artifact retrieval to fail.
  • Fixed an issue where plain text was losing formatting.

Jama

  • Fixed a bug that caused some artifact types to be missing when using a SOAP version.

Microsoft Team Foundation Server

  • Fixed an issue where artifact synchronization could halt if there was a problem establishing a TFS server connection. These connections are now retried.
  • Fixed an issue where the comment header was missing when synchronizing comments to Microsoft’s Team Foundation Server.
  • Fixed an issue where the TFS connector would sometimes stop processing items.
  • Fixed an issue causing failure to retrieve a TFS artifact when it contains weblinks with angle brackets.
  • The options for the Work Item Type field now have a stable identity.
  • Fixed an issue where the TFS connector allowed Test Result and Test Point as targets for workitem-only links, which caused failure from the server. A fix was introduced to indicate to products that only workitems can be link targets for those link fields.
  • Fixed an issue with retrieving large attachments from Microsoft’s Team Foundation Server.
  • Fixed an issue where ‘Wrong data type’ errors were not being retried by the Microsoft TFS connector.
  • Fixed an error that would prevent users from saving a VSTS Task collection. Users can resolve the error by updating to a newer version of the Microsoft TFS SDK library.

 

Upgrade Notes:

General

  • Tasktop Sync has an install wizard which will prompt all necessary configuration during install.

 

Connector-Specific

Microsoft Team Foundation Server (SDK)

  • Schema refresh is required for all TFS repositories in order to get all the available options to show up. As well, any attribute mappings involving the Work Item Type (System.WorkItemType) field will need to be remapped.
  • No migration is required for customers having previous artifacts synced from an on-demand server. Where the Location field is included in a mapping, proxy artifacts may be unexpectedly updated when non-mapped TFS field values are updated. A TFS artifact’s Location field will not update to the correct URI until changes are detected in the TFS artifact.
  • After upgrading Tasktop Sync or Tasktop Dev, the user will need to edit the TFS task repository settings. The user should be prompted to upload a new version of the TFS SDK. From https://github.com/Microsoft/team-explorer-everywhere/releases/tag/14.120.0, upload file “TFS-SDK-14.120.0.zip”.


Jama Integration Hub (JIH) UPGRADE VERSION 4.11.15

Published: 2017/10/25 

Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

Summary: This release contains fixes for CA Agile Central (Rally), HP, and TFS.

 
Fixes since JIH 4.11.11

Connector-Specific Fixes

CA Agile Central (Rally)

  • Connector will now check for errors parsing payloads and throw a specific exception for the operation to be retried.

HPE ALM

  • Fixed an issue with error handling in the HPE ALM/QC connector.

Microsoft TFS

  • Fixed an issue where artifact synchronization could halt if there was a problem establishing a TFS server connection. These connections are now retried.


Jama Integration Hub (JIH) UPGRADE VERSION 4.11.11

Published: 2017/10/06
Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

Summary: This release contains bug fixes for HP, JIRA, and TFS. 

Fixes since JIH 4.11.8

Connector-Specific Fixes

Atlassian JIRA

  • Fixed an issue with retrieving sprint labels containing an equal sign in the Jira connector

HP ALM

  • Fixed an issue in HP ALM connector where operations were failing due to ‘Session does not exist’ error
  • Fixed an issue where requirements aren’t checked-in successfully after updating.

Microsoft Team Foundation Server

  • Fixed an issue where ‘Wrong data type’ errors were not being retried by the Microsoft TFS connector.
  • Fixed an issue with retrieving large attachments from Microsoft’s Team Foundation Server.


Jama Integration Hub (JIH) UPGRADE VERSION 4.11.4

Published: 8/22/2017 

Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

Summary: This release contains bug fixes for JIRA and TFS.

 

Fixes since JIH 4.11.1

General Fixes

  • Fixed an issue where invalid Task IDs and URLs were generated when upgrading to the latest Jira connector.
  • Fixed a bug where updates to the synchronization log database would erroneously output that 0 records had been updated, and added detailed diagnostic information to errors which occur during post installation database updated.
  • Added action to mark comments on selected tasks as synchronized, preventing existing comments from being synchronized in the future.

Connector-Specific Fixes

Atlassian JIRA

  • Improved feedback when entering incorrect credentials while creating a repository connection to Zephyr for JIRA Cloud.
  • Fixed an issue where deleted users would cause failures.

HP ALM

  • 73367: Improved the performance for listing options for the Subject field.
  • 73366: Fixed an issue where listing options for test folders would fail with an error about duplicate results.

Microsoft Team Foundation Server

  • Updated TFS connector documentation images.

Rally

  • 73315: Filtered out duplicate release options in the CA Agile connector.


Jama Integration Hub (JIH) UPGRADE VERSION 4.11.1

Published: 2017/08/01
Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

 Summary: This release contains bug fixes across connectors, and the ability for read-only fields in Jama's UI to be synced using the "Allow API Override" option for that field.

 

Features since JIH 4.10.6

General Features

  • Tasktop Sync supports Windows Server 2016.

Connector-Specific Features

Atlassian JIRA

  • Added support for Test Cycle start and end date in the Zephyr for JIRA connector.

HP ALM

  • Added support for the Test field Requirement Coverage.

Jama

  • Added support for the “Allow API Override” field for Jama connector. This allows fields to remain read only in the Jama UI, while being editable via the JIH. This may be used on the proxy field, for example, to prevent accidental user edits.
    • This option can be found in Jama Software's Admin page, under Item Types configuration. Edit the field intended to be read only, and then select "Allow API Overwrite" to allow JIH to make edits.
    • tihproxy.png

 

Fixes since JIH 4.10.6

General Fixes

  • Fixed an issue where some attributes may not be synchronized during proxy creation if the source task had been previously discarded or marked as synchronized.
  • Tasktop Sync ensures that all configured queries for each repository are run.
  • Fixed an issue where Sync chose the wrong project when JIRA key was used as a project name for another project.
  • No longer scanning log files, improving memory consumption.
  • After upgrading, Sync now prompts for missing ClearQuest credentials.

Connector-Specific Fixes

Atlassian JIRA

  • Descriptions and comments having tables in JIRA are now produced with improved accuracy. Previously some rich text constructs such as lists within table cells could produce tables that were incorrectly formatted.
  • Fixed an issue which would cause errors when processing rich text if there were newlines between square brackets
  • Fixed an issue where the comment field was not available as a JIRA transition attribute when there were no other fields.
  • Fixed an issue causing errors when wiki-style renderer is treated as plain text for text fields mapped to rich text fields.
  • Atlassian JIRA’s HTML to Confluence conversion can now handle lists within tables.

HP ALM

  • Fixed an issue where plain text was losing formatting.
  • Fixed an issue where duplicate Test Runs were created.
  • Fixed an issue where plain text was losing formatting.
  • Username and Password now may contain UTF-8 characters when using Basic Authentication.
  • Fixed an issue where incorrect number of requirements could cause folder corruption.
  • Tooltips are displayed now for the Comment Handling and Comment Date Format fields.

Microsoft Team Foundation Server

  • Fix failure retrieving a TFS artifact when it contains weblinks with angle brackets.
  • Fixes an issue where an unexpected authorization exception is thrown while retrieving project options.
  • Fix an issue where web links fields could not be synchronized into Microsoft Team Foundation Server
  • Fixed an issue that caused frequent “Connection factory has been shutdown” errors from Microsoft Team Foundation Server.
  • Fixed an issue in Microsoft Team Foundation Server connector that prevented schema migration when upgrading to new version.

Jama

  • Improved the error message when the connector tries to retrieve a folder that no longer exists.

Rally

  • Improved error handling when retrieving an artifact associated with a deleted user.

VersionOne

  • Fixed a problem where some requests to retrieve artifacts with long URLs caused errors due to length.
  • Fixed an issue where artifacts synchronized endlessly. 

Upgrade Notes:

  • Tasktop Sync has a new install wizard which will prompt all necessary configuration during install.

Connector Specific Upgrade Notes

Atlassian JIRA

  • Any existing custom text field in JIRA that is mapped to a RichText field in a collection will have to be re-mapped.
  • Unique identification of JIRA artifacts has changed and a migration of data will be required the first time this version of the application is run.

HPE ALM (SDK)

  • The Linked Test Runs field was once populated but has not been populated since support for linked Test Runs was added in the Linked Entities field. The Linked Test Runs field has now been removed. Customers who had previously mapped the Linked Test Runs field will need to add the Linked Entities field to mappings that don’t already include it.
  • Mappings for tests and test sets that include the Subject (TS_SUBJECT) or the Test Set Folder (CY_FOLDER_ID) attributes will need to be remapped if the mapping relied on the name of the Subject or Test Set Folder.

Jama

  • Schema refresh is required for all Jama repositories.

Microsoft Team Foundation Server

  • After upgrading Tasktop Integration Hub, the user will need to perform the following steps:
    1. Stop the application.
    2. Delete the old TFS SDK library from the Tasktop install. On Windows, the default path to the TFS SDK folder should be C:\ProgramData\Tasktop\libraries\microsoft-tfs. On Linux, the default path should be $INSTALL_FOLDER/libraries/microsoft-tfs, where $INSTALL_FOLDER is the root of the product install.
    3. Start the application.
    4. Go to the TFS repository in the application. The product should prompt the user to upload a new version of the TFS SDK. From https://github.com/Microsoft/team-explorer-everywhere/releases/tag/14.118.0, upload file “TFS-SDK-14.118.0.zip”. After upgrading Tasktop Sync or Tasktop Dev, the user will need to edit the TFS task repository settings. The user should be prompted to upload a new version of the TFS SDK. From https://github.com/Microsoft/team-explorer-everywhere/releases/tag/14.118.0, upload file “TFS-SDK-14.118.0.zip”.
  • Schema refresh is required for all TFS repositories in order to get all the available options to show up.
  • No migration is required for customers having previous artifacts synced from an on-demand server. Where the Location field is included in a mapping, proxy artifacts may be unexpectedly updated when non-mapped TFS field values are updated. A TFS artifact’s Location field will not update to the correct URI until changes are detected in the TFS artifact.

Rally (SDK)

  • Some HTML fields have been changed to plain text fields. After refreshing repository schema field values will not be rendered as HTML as they were previously. Mappings may need to be updated.
    • Any customer upgrading from 4.7.1 and higher and has used the project scoped query with an “owner” choice populated, will have to recreate this query. This will not affect customers upgrading from earlier than 4.7.1

VersionOne

  • Customers integrating VersionOne may experience one time synchronization of all artifacts.


Jama Integration Hub (JIH) UPGRADE VERSION 4.10.2

Published: 2017/06/08
Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

 Summary: This release contains minor updates to HP ALM and TFS.

Features since JIH 4.10.2

Connector-Specific Features

HP ALM

  • Added support for the Test field Requirement Coverage.

 

Fixes since JIH 4.10.2

Connector-Specific Fixes

HP ALM

  • Fixed an HP ALM issue where plain text was losing formatting.

Microsoft Team Foundation Server

  • Fixed an issue that caused frequent “Connection factory has been shutdown” errors from Microsoft Team Foundation Server.



Jama Integration Hub (JIH) UPGRADE VERSION 4.10.2

Published: 5/3/17

Important Upgrade Note: If you are using Jama on-premises 8.12 - 8.14, please update to 8.14.1 or later before taking this update to ensure API compatibility.

Summary: This release contains additional software version support, general and connector-specific fixes, and enhancements for all connectors.

Features since JIH 4.9.9

General Features

  • Fixed an issue where Sync chose the wrong project when JIRA key was used as a project name for another project.
  • Added patent information to Tasktop Sync

Connector-Specific Features

Atlassian JIRA

  • Cycle field was changed from a ValueWithLabel field to an ArtifactLink field
  • Added support for JIRA Zephyr Test Cycle as an artifact type.
  • Custom URL field added to JIRA connector

Jama

  • Version field added to Jama connector.

Fixes since JIH 4.9.9

General Fixes

  • Handling PersonNotFoundException during synchronizations, allowing synchronization to continue.
  • Now correctly matching comments when the comment header contains a non-breaking space.
  • Fixed an issue where email notifications could not be configured.
  • Fixed an issue where an attribute in both an ‘always’ attribute mapping and a scripted attribute handler always executed the script, regardless of whether it changed.
  • Fixed an issue where Tasktop Sync freezes when sending error email.

Connector-Specific Fixes

Atlassian JIRA

  • Fixed an issue where the comment field was not available as a JIRA transition attribute when there were no other fields.
  • Fixed an issue causing errors when wiki-style renderer is treated as plain text for text fields mapped to rich text fields.

HP ALM

  • Fixed an issue where incorrect number of requirements could cause folder corruption.

Jama

  • Fixed an issue where listing deleted folders threw an ArtifactNotFoundException instead of ContainerNotFoundException.

Microsoft Team Foundation Server

  • Fixed an issue in Microsoft Team Foundation Server connector that prevented schema migration when upgrading to new version.

Rally

  • Improved error handling when retrieving an artifact associated with a deleted user.

VersionOne

  • Fixed an issue where artifacts synchronized endlessly.
  • Fixed a problem where some requests to retrieve artifacts with long URLs caused errors due to length.

Upgrade Notes

General

  • Tasktop Sync has a new install wizard which will prompt all necessary configuration during install.

Connector-Specific Upgrade Notes

Atlassian JIRA

  • Any existing custom text field in JIRA that is mapped to a RichText field in a collection will have to be re-mapped.

HPE ALM (SDK)

  • The Linked Test Runs field was once populated but has not been populated since support for linked Test Runs was added in the Linked Entities field. The Linked Test Runs field has now been removed. Customers who had previously mapped the Linked Test Runs field will need to add the Linked Entities field to mappings that don’t already include it.
  • Mappings for tests and test sets that include the Subject (TS_SUBJECT) or the Test Set Folder (CY_FOLDER_ID) attributes will need to be remapped if the mapping relied on the name of the Subject or Test Set Folder.

Jama

  • Schema refresh is required for all Jama repositories.

Microsoft Team Foundation Server (SDK)

  • Schema refresh is required for all TFS repositories in order to get all the available options to show up.
  • No migration is required for customers having previous artifacts synced from an on-demand server. Where the Location field is included in a mapping, proxy artifacts may be unexpectedly updated when non-mapped TFS field values are updated. A TFS artifact’s Location field will not update to the correct URI until changes are detected in the TFS artifact.

Rally (SDK)

  • Some HTML fields have been changed to plain text fields. After refreshing repository schema field values will not be rendered as HTML as they were previously. Mappings may need to be updated.
  • Any customer upgrading from 4.7.1 and higher and has used the project scoped query with an “owner” choice populated, will have to recreate this query. This will not affect customers upgrading from earlier than 4.7.1

VersionOne

  • Customers integrating VersionOne may experience one time synchronization of all artifacts.

Jama Integration Hub (JIH) UPGRADE VERSION 4.9.9

Published: 4/13/2017 (Download Jama Integration Hub - Jama Software )

Summary: This release contains general fixes.

Fixes since JIH 4.9.8

General Fixes

  • Fixed an issue where Sync chose the wrong project when JIRA key was used as a project name for another project.

Connector-Specific Fixes

HP ALM

  • Fixed and issue where linked entities could not be updated.

Jama

  • Fixed an error that would occur when Sets have the exact same lastActivityDate.
  • Fixed a problem where updating a field value can overwrite another field’s value in Jama.

Microsoft Team Foundation Server

  • Fixed an issue where attachments could not be retrieved.


Jama Integration Hub (JIH) UPGRADE VERSION 4.9.8

Available 2017/04/04


Summary:
This release contains general fixes.

Fixes since JIH 4.9.7

General Fixes
  • Handling of PersonNotFoundException during synchronizations, allowing synchronization to continue.

Connector-Specific Fixes

Atlassian JIRA

  • Fixed an issue where the JIRA connector did not return a valid label for single-select options in closed issues.
  • Fixed an issue retrieving sprint value when multiple sprint fields are defined in Atlassian JIRA.

HP ALM

  • Fixed an issue where expired sessions are not re-authenticated.
  • Fixed an issue where the root elements of Lookup list fields with sub-items were not available.

Jama

  • Fixed an issue with reading error messages from Jama.

Rally

  • Fixed an issue where network errors from CA Agile Central were not automatically retried.


Jama Integration Hub (JIH) UPGRADE VERSION 4.9.7

Available 2017/03/22 
Summary:
This release contains general fixes, and fixes for the HP ALM connector.

Fixes since JIH 4.9.6
General Fixes
  • Now correctly matching comments when the comment header contains a non-breaking space.
  • Logging of successful operation metrics is only available in TRACE log level.
Connector-Specific Fixes
HP ALM
  • Fixed an issue where UI field text wrapping was inserting false line breaks.
  • Fixed an issue in HPE ALM where an error would occur retrieving a list of test folders while test folders are being created or removed on the server.


Jama Integration Hub (JIH) UPGRADE VERSION 4.9.6

Available 2017/03/15

Summary: This release contains fixes to the HP ALM connector.

Connector-Specific Fixes since JIH 4.9.4:

HP ALM

  • Fixed an issue in HPE ALM where an error would occur retrieving a list of test folders while test folders are being created or removed on the server.
  • Improved performance when retrieving test folders and test set folders.
  • Fixed an issue where HP ALM parent link was allowed to be set to an invalid value.



Jama Integration Hub (JIH) UPGRADE VERSION 4.9.4

Published: 2017/02/21

Summary: This release contains bug fixes for JIRA and Rally. 

Connector-Specific Fixes since JIH 4.9.2:

Atlassian JIRA

  • Fixed an issue so that the Atlassian JIRA connector’s person search is no longer too broad for some JIRA configurations involving LDAP.

Rally

  • To improve Tasktop performance, CA Central Agile collections are scoped by project and not an entire workspace.

 

Upgrade Notes

Rally

  • Routing for CA Central Agile is now done with projects directly, not workspaces. Collections will need to be re-created and corresponding integrations updated.



Jama Integration Hub (JIH) 4.9.2, available February 14, 2017 

Summary: This release contains major bug fixes for all tools.

Features since 4.8.5:

Atlassian JIRA

  • Added support for JIRA nFeed plugin fields.
  • Added USERNAME person field support.

Rally / CA Agile

  • The CA Agile Central connector now treats Workspace as a top-level Project and allows artifacts to move across projects.
  • Added Changeset support for CA Agile Central.
  • Summary and formatted ID for linked tasks are now shown in the task editor.

 

General Fixes since JIH 4.8.5:

  • Fixed examples and updated Tasktop Sync help documentation for external value mappings.
  • Fixed an issue where some errored contexts which have fallen out of scope may be requeued without a warning that they will not be immediately retried.
  • Fixed an issue where script validation caused performance issues in Sync Studio UI.
  • Fixed an exception that happened in filtered task link synchronizing when a linked task falls out of task mapping scope.
  • Fix an issue in the Error Report where the wrong logs would get downloaded.
  • Users can now import a new license during the Post Installation wizard.
  • Resolved an issue caused by a missing task id in the database during post installation schema migration.
  • Resolved issue migrating old, invalid tasks during post installation.
  • Changes made by chained transitions are ignored before the final transition.
  • Fixed an issue where Tasktop Sync was unable to sync an item to another system when the comment was too long.
  • Fixed an issue causing status transition caster errors during proxy creation for connectors which have the status field on the creation scheme.
  • Fixed an issue where filtered task link synchronization was not filtering links to non-mapped tasks.
  • The Tasktop Sync Web UI now correctly displays the state of the comment synchronization as it is seen in the Tasktop Sync studio.
  • The Tasktop Sync Web UI now displays all configuration elements for template-based task mappings.
  • Fixed an issue where users using older browsers would be unable to create OSLC task link using the Tasktop OSLC adapter.

 

Connector Specific Fixes since JIH 4.8.5:

Atlassian JIRA

  • Fixed error that occurred during JIRA authentication.
  • Fixed a problem when retrieving a JIRA artifact with unsupported writeable fields.

Jama

  • Fixed an issue where an attribute in both an ‘always’ attribute mapping and a scripted attribute handler always executed the script, regardless of whether it changed.
  • Fixed an issue where Tasktop Sync freezes when sending error email.
  • Fixed an issue with synchronizing lists in rich text fields in Jama.
  • Fixed an issue where Jama items without names could not be retrieved.
  • Fixed an issue where some server-side exceptions were being reported with confusing messages.
  • Fixed an issue where the Jama connector failed to update relationships on locked artifacts.
  • Fixed an issue where locked items were causing all items being synchronized to go into pending state.
  • Fixed an issue where item types that contained fields already on the Core type could not be synchronized.

HP ALM

  • Fixed an issue where link retrieval failed on changing total number of records.
  • Fixed an issue where HPE ALM Test Sets would display an incorrect location.
  • Fixed an issue where data integrations would take a long time processing artifacts with a complex folder structure.
  • Fixed an issue in HP ALM connector where some URL attachment based web links would display missing or incorrect URLs.
  • Fixed an issue in the HP ALM connector where sometimes attachments were incorrectly being treated as web links.
  • Fixed an issue with incorrect links when artifacts have the same ID.
  • Fixed an issue where Test Configuration parent Tests were not being checked out.
  • Fixed an issue where comments with no header couldn’t be retrieved.

Microsoft Team Foundation Server

  • The required version of Team Foundation Server SDK for Java has changed from 12.0.2 to 14.0.2.
  • Fixed memory consumption issues with the TFS SDK.
  • Fixed an issue where date-based favorite queries return no result.

CA Agile / Rally

  • CA Agile Central Collections in Tasktop Integration Hub need to be re-created to accommodate improvements in Workspace/Project containment support.
    Duplicated Workspaces in the Project selection dialog is a symptom of an outdated CA Agile Central Collection.
  • Fixed an issue where some CA Agile Central single/multi-select fields did not have all options available.
  • Fixed an issue in Portfolio Item in CA Agile Central that affected subtask creation.
  • The Index field of CA Agile Central Task artifacts is no longer required, defaults to zero, and is hidden in the application.
  • Fields in CA Agile Central that can contain HTML but are not always displayed in the UI as HTML are now represented as plain text fields. After refreshing repository schema field values will not be rendered as HTML as they were previously. Mappings may need to be updated.
  • Fixed an error sometimes seen when synchronizing newly created artifacts with parent child links.
  • Fixed an issue where the project field of CA Agile would give an error stating that project name is not a mapped option.

VersionOne

  • Fixed an issue where the PlannedEnd and PlannedStart fields weren’t in the schema.

 

UPGRADE NOTES:

HPE ALM (SDK)

  • The Linked Test Runs field was once populated but has not been populated since support for linked Test Runs was added in the Linked Entities field. The Linked Test Runs field has now been removed. Customers who had previously mapped the Linked Test Runs field will need to add the Linked Entities field to mappings that don’t already include it.
  • Mappings for tests and test sets that include the Subject (TS_SUBJECT) or the Test Set Folder (CY_FOLDER_ID) attributes will need to be remapped if the mapping relied on the name of the Subject or Test Set Folder.

Jama

  • Schema refresh is required for all Jama repositories.
  • For the most recent fixes to Jama rich text processing, any configurations mapping a Jama rich text field using HTML as the markup language should be changed to use Jama HTML instead.

Microsoft Team Foundation Server (SDK)

  • Schema refresh is required for all TFS repositories in order to get all the available options to show up.
  • No migration is required for customers having previous artifacts synced from an on-demand server. Where the Location field is included in a mapping, proxy artifacts may be unexpectedly updated when non-mapped TFS field values are updated. A TFS artifact’s Location field will not update to the correct URI until changes are detected in the TFS artifact.

Rally (SDK)

  • Some HTML fields have been changed to plain text fields. After refreshing repository, schema field values will not be rendered as HTML as they were previously. Mappings may need to be updated.
  • Any customer upgrading from 4.7.1 and higher and has used the project scoped query with an “owner” choice populated will have to recreate this query. This will not affect customers upgrading from earlier than 4.7.1.

 


Jama Integration Hub (JIH) 4.8.5, available December 6, 2016
 

Summary: This release contains better error handling, and better handling of tasks that fall out of a mapping scope.

General Fixes since JIH 4.8.3:

  • Fixed an exception that happened in filtered task link synchronizing when a linked task falls out of task mapping scope (SOS-DEF-1533). 

Connector Specific Fixes since JIH 4.8.3:

Jama

  • Fixed an issue where some server-side exceptions were being reported with confusing messages.

Jama Integration Hub (JIH) 4.8.3, available November 22, 2016

Summary: This release contains bug fixes resolving issues around upgrading. 
  • Resolved an issue caused by a missing task id in the database during post installation schema migration.
  • Resolved issue migrating old, invalid tasks during post installation.

 
Connector Specific Fixes since JIH 4.8.1:

Jama

  • Fixed an issue where the Jama connector failed to update relationships on locked artifacts.

Jama Integration Hub (JIH) 4.8.1, available November 2, 2016 

Summary: This release contains bug fixes and minor updates. 

Features: Attribute proxy stores can now be configured to use attributes identified through label.
OSLC queries support connector schema migration during workspace upgrade.
Task mapping conditionals can be constructed using attribute-label and value-label to reference attributes and value options by label.
Installation upgrade startup tasks are now handled in one post installation wizard.
Individual synchronized task pairs can be configured so that new changes will not be synchronized from the Sync Tasks view, the Web UI, or the dashboard Error Queue.
 
Connector Specific Fixes since JIH 4.7.10:
Atlassian JIRA

  • Fixed an issue where content in the description field longer than 32,767 bytes caused synchronization failures.
  • Atlassian JIRA connector now supports Zephyr Test Executions in versions of JIRA earlier than 7.0.

Jama

  • Fixed an issue where test case steps were being erased when using the REST version of the connector.
  • Fixed an issue where Test Cases with Test Steps could not be retrieved.
  • Fixed an issue where Last Activity Date was not appearing in the schema.
  • Improved error message when APIs are disabled or account is locked.
  • Jama REST Client can detect read-only custom fields.

Sparx Systems Enterprise Architect

  • Sparx EA connector now supports MS SQL encrypted database connection strings.
  • Fixed an issue where Sparx EA processes that were not ended correctly caused memory issues.

Upgrade Notes

  • Tasktop Sync has a new install wizard which will prompt all necessary configuration during install.
  • HP ALM: The Linked Test Runs field was once populated but has not been populated since support for linked Test Runs was added in the Linked Entities field. The Linked Test Runs field has now been removed. Customers who had previously mapped the Linked Test Runs field will need to add the Linked Entities field to mappings that don’t already include it. Mappings for tests and test sets that include the Subject (TS_SUBJECT) or the Test Set Folder (CY_FOLDER_ID) attributes will need to be remapped if the mapping relied on the name of the Subject or Test Set Folder.
  • Jama: Users will need to refresh schema.
  • Microsoft Team Foundation Server: Refreshing the schema might be necessary in order to get all the available options to show up.No migration is required for customers having previous artifacts synced from an on-demand server. Where the Location field is included in a mapping, proxy artifacts may be unexpectedly updated when non-mapped TFS field values are updated. A TFS artifact’s Location field will not update to the correct URI until changes are detected in the TFS artifact.
  • Rally: Some HTML fields have been changed to plain text fields. After refreshing repository schema field values will not be rendered as HTML as they were previously. Mappings may need to be updated. Any customer upgrading from 4.7.1 and higher and has used the project scoped query with an “owner” choice populated, will have to recreate this query. This will not affect customers upgrading from earlier than 4.7.1

See the JIH Supported Environments & Integrations page for compatible software and recommended server environments.



Jama Integration Hub (JIH) 4.7.10, available October 19, 2016


Summary: This release contains bug fixes and minor updates. 

Connector Specific Fixes since JIH 4.7.9:
Jama

  • Fixed an issue where a URL attribute mapped to a custom Jama Text Field incorrectly (SOS-DEF-1407).

See the JIH Supported Environments & Integrations page for compatible software and recommended server environments.



Jama Integration Hub (JIH) 4.7.9, available September 22, 2016

Summary: This release contains bug fixes that resolve issues retrieving Jama's Last Activity Dates, and an issue updating Jama Test Steps. 

Connector Specific Fixes since JIH 4.7.7:
Jama

  • Fixed an issue where Last Activity Date was not appearing in the schema.
  • Fixed an issue where Test Cases with Test Steps could not be retrieved (SOS-DEF-1349).
  • Fixed an issue where Test Steps were incorrectly updated (SOS-DEF-1364).

Upgrade Notes


Microsoft Team Foundation Server

  • Refreshing the schema might be necessary in order to get all the available options to show up.




See the JIH Supported Environments & Integrations page for compatible software and recommended server environments.




Jama Integration Hub (JIH) 4.7.7, available September 13, 2016 


Summary: This release contains a bug fix that resolve issues retrieving Jama test cases and test steps. 

Connector Specific Fixes since JIH 4.7.2:
Jama


  • Fixed an issue where Test Cases with Test Steps could not be retrieved  (SOS-DEF-1349).

See the JIH Supported Environments & Integrations page for compatible software and recommended server environments.




Jama Integration Hub (JIH) 4.7.2, available August 15, 2016 

Summary: This release Fixes an issue with Sparx Enterprise Architect causing memory issues, and adds support for the latest Atlassian JIRA release (7.1.9). 

Connector Specific Fixes:
Sparx Systems Enterprise Architect (SDK)


  • Fixed an issue where Sparx EA processes that were not ended correctly caused memory issues.
  • Fixed an issue where sub-requirements were not being retrieved when searching by package.

Upgrade Notes


  • After a Sync upgrade, when you start Sync for the first time, you may be presented with a Wizard that will complete the Sync upgrade. As always, it is highly recommended that you back up your Sync workspace before starting the upgrade. In the new wizard, you may be forced to enter repository credentials before the upgrade continues. Once all repositories are valid, your repository data will be updated automatically.
  • If you were using the "-groovyClasspath" command line argument to expand the classpath for Groovy scripts, this is no longer supported. Instead, move the *.jar files into a directory named "dropins" inside the workspace.
  • Tasktop Sync will no longer start if Task Mappings are configured with extra fields in the repository scope.

See the JIH Supported Environments & Integrations page for compatible software and recommended server environments.

Jama Integration Hub (JIH) 4.6.6, available July 14, 2016


Summary: This release Fixes an issue where writing a TFS work item will fail because the Automation Status field is not available.

See the JIH Supported Environments & Integrations page for compatible software and recommended server environments.

Jama Integration Hub (JIH) 4.6.4, available June 16, 2016 

Summary: This release contains bug fixes that allow Microsoft Visual Studio Online to work with Microsoft's latest updates.


Connector-specific fixes since JIH 4.6.1:

Microsoft Team Foundation Server (SDK)

  • Fixed handling of new Microsoft Visual Studio Online URL that was resulting in HTTP 404 errors.

JIH 4.6.4 has support for the following tools:


Jama Integration Hub (JIH) 4.6, available May 2016


Known issues:
Due to known issues, upgrades to this version should not be performed if:
The “current project” scope in Jama filters is used to map between Jama and other tools
Your organization uses OAuth to authenticate users
Your organization uses SAML to authenticate users and plans to enable REST in the near future

Jama is working on remedies for these issues and will post updates as they are resolved

Organizations can use SAML/Oauth with the JIH, however, an additional connector user needs to be created. Please contact Jama Support before mapping the JIH.

New Features
New Connectors
Bugzilla connector now available!
Sparx Enterprise Architect connector now available!
You can now create process models and requirements in Sparx EA and mirror those requirements in a full-featured requirements management system such as Jama or DOORS.

Core JIH Features

  • External ARM links display artifact name instead of URL This configuration setting makes links to artifacts in other systems much more user-friendly. 
  • Highlight required attributes Required attributes are now at the top of the attribute mapping drop down and are flagged with an asterisk. 
  • Some query, task and repository wizard fields now support auto-completion, filtering options by typed text using case insensitive matching to any contiguous portion. 
  • When working with a non-default authenticator, the credential fields have been moved down to the authentication settings section. 
  • The Task Link to Task Link filtering now performs an extra check to see if the task ID is also on one of the mapping's queries. 
  • Now storing full Synchronization logs as separate files in the sync workspace. 
  • A warning message is displayed at the top of the mapping editor when there are required attributes in need of mapping. 
  • Database proxy and performance warnings are now displayed as info level statuses. 
  • Tasktop Sync presents warnings to users using task attributes in the configuration for the task link to external link caster. 
  • The Task Link to External Link caster now supports inserting the values of linked task attributes on the external link labels being synchronized. 
  • The Task Link to External Link caster now supports setting the label of the External Link during synchronization. 
  • When picking an attribute from the drop down in the Attribute Mappings page, attributes in need of mapping are at the top and starred. 

TFS

  • External ARM support for Changesets.
  • Tree-based queriesWe’ve added support for customers that want to create a weblink to a changeset in another system.
  • You can now use any type of query that’s configured in TFS as a Sync query (flat list, link type, tree type).

HPQC / ALM

  • We’ve added Test Set, Test Run and Test Instance to our already existing support for Test Case and Test Configuration. 
  • HP ALM allows the use of a web address as attachment type, so we’ve added support for this.

Bug Fixes
Core JIH Fixes

  • Some network operations, including queries, will be re-executed automatically when authorization expires. 
  • Tasktop Sync truncates validation messages to ensure errors do not occur for very lengthly validation messages.
  • Improved handling of periodic repository authentication errors. 
  • Added configuration of repository back-off to settings. 
  • Fixed error in SyncStateManager. 
  • The Web UI dashboard will now show the same task mapping listing as the Services view. 
  • Tasktop Sync's status transition caster can now be used with source attributes other than the standard status attribute. 
  • Expired perpetual licenses will no longer result in error messages but instead with info messages informing that product support and maintenance has ended. 
  • Tasktop Sync will only allow the user to configure attachment or comment synchronization if the repositories being synchronized support the synchronization. 
  • Sync will stop submitting the same change after 5 attempted failures.


Connector-Specific Fixes

Jama

  • Fixes an issue where queries were not returning all expected itemsJama sequence field now correctly populated when using SOAP. 
  • Fixed the URL used to retrieve attachments for Jama REST repositories. 
  • Fixed error that occurs when retrieving a user with an empty name in Jama. 
  • Fixes an issue where duplicate items could be created when item creation in Jama fails.




Upgrade Notes: Upgrading from the Previous Versions of Sync

HP ALM: HP ALM Connector now considers "Users List" fields that are not "Verified" as text fields instead of person fields.

JIH 4.6 has support for the following tools:





Jama Integration Hub (JIH) 4.5.7, available April 2016 

Summary: With this release many complex data syncing scenarios can now be handled through the JIH mapping interface. With the addition of new casters, the JIH can sync web links to other web links, to string fields, and to location/URL data. Schema refreshing now gives users more flexibility to update schemas; by refreshing using locally stored data for minor item changes rather than accessing the source repository schema refresh performance may be greatly improved.

Due to known issues, upgrades to this version should not be performed if:
-the “current project” scope in Jama filters is used to map between Jama and other tools
-your organization uses OAuth to authenticate users
-your organization uses SAML to authenticate users and plans to enable REST in the near future 

New Connector Features
Core JIH Features


  • Mapping and Casters Improvements:
    • The comment author can be prepended to each synchronized comment.

    • For example, if this setting is enabled and the user John Smith This is a comment then the comment will appear as the following in the target repository: (Comment by John Smith) This is a comment
    • Enabling this setting will cause the author header to be added to every new comment synchronized into this repository. Previously synchronized comments will not be modified.
    • Added ability to refresh available options from the new query creation dialog.
    • The Refresh button re-runs the existing query and pulls in new artifacts.
    • Example scenario: User is in the mapping creation flow, and just added a new field to Jama after staring the mapping creation. The recommendation is that after creating a new field or value, create a new Jama artifact, and then click on refresh. That will pull in the new artifact and Sync will recognize that there's a new field and will generate a new schema.

    • The Web Link to String caster is available for use via the mapping editor. If you need to synchronize web URLs from one repository to another, but your target repository does not support attached web URLs, use this caster.

    • The Location to Web Link caster is available. It allows the web link label to be customized (e.g. Show the key Task123 www.yourinstance.com/task123). If you need to have the URL of the source task as a web link on the target task, use this caster. This caster will create a web link, which points to the source task, on the target task.




      • The Web Link to Web Link caster is available via the mapping editor.
      • The Task Link to Task Link caster can now be configured to only synchronize links to tasks within scope of an existing Task Mapping. When this option is checked, JIH will first validate if the related item matches any mapping, and only includes the link if it does. All references to items that do not match a mapping will be ignored. (Note that “Task Link” = “Relationship” in Jama’s terms)

      • The Status Transition caster allows complex status synchronization to be configured via mapping editor. Suggested status transition mappings will be presented.
      • Transition-specific attribute synchronization can now be configured in the mapping editor. These mappings write to attributes required during a transition, such as a resolution attribute for a transition between the In-Progress state and the Done state.
    • The Value to Task Link caster supports synchronization between task links (relationships) and single select fields.

        • One attribute in the mapping must be of the type “Single Select” or “Multi Select.”
        • One attribute in the mapping must be of the type “Task Dependency.”
      • Value mappings can be generated automatically between values which are similar by clicking the Suggest mappings... button.




      • Required and Read Only metadata now visible on mapping editor schema page.

    • Performance
      • Performance improvements were made allowing schema refresh without need for query execution for supporting repositories.
    • Indicators and Warnings:
      • Unmapped values are highlighted in yellow in the caster's UI and implicit mappings are shown as grey and italicized. Mapping editor now provides warnings when required attributes are not mapped, and when read only attributes are mapped.




      • Synchronization conflicts that result in no synchronization will be included in error emails.
      • When queries fail to execute, error email notifications will include more details related to the query in error.
      • The error displayed when an incoming task matches multiple mappings now shows the name of each mapping.
      • A warning email will now be sent when disk space is low.
      • A warning label will be displayed at the top of the Transition Caster user interface if there is a mapped transition with required transition attributes which are not mapped.
      • The Error Log view can now be opened via a menu option in the toolbar dropdown menu.
      • Users can now clear synchronizations in the error queue from Web UI.
      • The contents of error notification emails can now be configured.
      • All repositories, queries, and tasks are now presented in the Sync Tasks view. The Task Repositories view is no longer available.
    • Scheduled Jobs and other Configuration:
      • When “Use auto-comment user on validation failure” is selected the mapped authors of comments will be validated to determine if they exist in the target repository, if they do not exist the auto-comment user will be used as the author on submission.
      • Refresh Schema button in schema editor page now allows quick refresh based on locally cached data or optionally refreshing from the repository.
      • Synchronizations are now placed into Pending for a longer period if required by the repository.
      • A new scheduled job is available that marks all tasks in a query for synchronization.
      • A configuration option is now available to validate the authors of comments and attachments.
      • The maximum number of tasks to be used for schema refresh and generation is now configurable via preferences.

    • Administrators can now recreate a synchronized task should one be deleted by an end user.

      • It is now possible to automatically initiate shutdown of the application if disk space is running low.
      • Repository comment impersonation capabilities now automatically detected.
      • Repository URLs must now be changed through the Change Repository URL Wizard.
      • Support has been added for the migration of a synchronized project to another server.

    JIRA Connector Features

    • JIRA connector now supports fields like "watchers," "comments," and custom single-selects on JIRA OnDemand and JIRA 7.1.0.
    • JIRA connector now supports sub-tasks.
    • Performance improvements in the JIRA connector by caching information that is repeatedly retrieved.
    • The JIRA connector now supports authentication using CA Single Sign-on.

    HP QC / ALM Connector Features

    • Added support for Latin character encodings in attachment file names.

    Rally Connector Features

    • Rally Connector specific http headers are now included in all http requests.

    Bug Fixes
    SOS-DEF-256/SOS-BUG-676: If pre-defined fields such as Status have different Pick Lists associated with them, the JIH will not always populate the proper field values (35119).
    SOS-DEF-647: If an empty value is set to always update, a max synchronization error will be thrown and the item won't update. JIH will no longer attempt to submit unchanged attributes (32623).

    JIH Core Fixes

    • Fixed an issue where Tasktop Sync would fail to synchronize changed attachments.
    • Fixed an error in the Tasktop Sync documentation for the Attribute Based Person Mappings example.
    • Fixed UI scrolling problem with multi-select fields in query wizard.
    • Fixed an issue where invalid enumeration lists in the schema prevented Sync from starting.
    • Scheduled Jobs will work in locales using commas instead of periods for decimal formatting.
    • Line Breaks will automatically be removed from Attachment Descriptions and Titles if not supported.
    • Fixed an issue that caused Sync to report an error about aborting requests to secure storage.
    • Tasktop Sync can now be started without its internal web server (web/oslc capabilities disabled).
    • Improved handling of attribute changes while state transitions happen concurrently.
    • Tasktop Sync will ensure that tasks whose data failed to download are re-downloaded
    • Improved handling of Time Worked entries with zero duration.
    • Fixed No More Handles issue stemming from Connector branding image duplication.
    • Users can now copy text from the Connector Requirements descriptions in wizards.
    • Sync will apply any mapping whose strategy is "Apply Always" during every submission.
    • Metrics email now reports "Synchronizations" and "Created"
    • Fixed an issue where template mappings would fail to load the attribute mapping editor.
    • Switching multiple mappings to a new template will only write to the configuration file once when all mappings have been updated.
    • Improved performance of Sync schema generation for SDK connectors.
    • Tasktop Sync will no longer attempt to submit unchanged attributes.
    • Improved responsiveness of New Mapping from Mapping Template wizard.
    • Tasktop Sync can now read Time Worked entries with missing information
    • Tasktop Sync will only display errors and warnings for the currently in use configuration files.
    • Scripted Attribute Handlers can now specify the attributes they handle. The specified attributes will be considered as having been mapped with no 'required' field warnings being shown for these attributes.
    • When running as a service, if a lock on the runtime workspace cannot be acquired the process will end.
    • Improved handling of periodic repository authentication errors.
    • Fixed error in SyncStateManager.

      Upgrade Notes:Upgrading from the Previous Versions of Sync

      • Upon upgrading you will be required to perform a database update. This will be performed automatically and is required before continuing.
      • The Error Log is no longer opened by default in new workspaces. The Error Log may be accessed via the Tasktop Sync toolbar dropdown menu.
      • Error notifications are now scheduled to execute every hour. This schedule is configurable through the mapping editor.

      • Jama Connector Specific Upgrade Notes:
        • Please update the Jama schema via the corresponding schema tab of the mapping editor.
        • After a schema refresh, a warning may appear in configuration about "Expected comment type of...". To resolve, select the identified comment content-type in the mapping editor.
      • HP ALM Connector Specific Upgrade Notes:
        • For comment impersonation into HP ALM, the user has to exist and be properly mapped now. Prior to adding this feature, invalid users could be used for impersonation into HP ALM comments. Now, this is not working anymore.
        • HP ALM Connector now considers "Users List" fields that are not "Verified" as text fields instead of person fields.

      JIH 4.5.7 has support for the following tools:



      Jama Integration Hub (JIH) UPGRADE VERSION 4.3.12, available December 2015 [Download here]

      Connector-Specific Fixes
      Atlassian JIRA
      Atlassian JIRA connector now supports fields like "watchers", "comments" and custom single-selects on Atlassian JIRA Cloud and Atlasssian JIRA 7.1.0.
       
      The JIH has support for the following tools:



      Upgrade Steps
      Important Note: If upgrading from JIH 4.2 or earlier, mappings no longer require a set to be specified. If you did not upgrade to 4.3, you will need to revisit old mappings. This allows mappings to be scoped by project rather than set, reducing the overall number of mappings required. Please see the 4.3 releases notes below regarding Relaxing Set Scope Requirement.
       
      The upgraded version of Tasktop Sync will have access to all your existing repositories, queries and configurations. To upgrade an existing installation, follows these steps:
      1. Stop JIH sync and close the application.
      2. Uninstall the existing Tasktop Sync version using the Uninstall



      #releasenotes #JIH
      27 comments
      1355 views

      Comments

      11-23-2016 12:12

      JIH 4.8.3 is now available.

      04-29-2016 18:21

      Yay! That's good to hear.

      04-29-2016 12:44

      Just upgraded the latest version without problems.

      The new 'Status Transition caster' is a great improvement over the existing one

      04-29-2016 12:14

      Clear answer Ryan, thanks!

      04-29-2016 12:04

      "Traditional Project" is the name of an actual physical project that comes with Jama; the "current project" Anna's referring to is basically just a pointer, to "whatever project I'm currently in when I run the filter".

      i.e. If you have projects in Jama called "Project1", "Project2" and "Project3" which happen to have similar types of items in them, Jama lets you define a single filter which can work with any of those three projects, by creating the filter with a criteria of current project.

      If you're inside Project1 when you run the filter, "current project" == "Project1", so the filter returns only the matching items from Project1. If you're inside Project2, the filter only returns the matching items from Project2, and so on.

      (This functionality is useful for when you have multiple projects with similar item types, and don't want to bother to have to copy the filter multiple times to get it to work for each of the different projects)

      In any case, if you examine all of the filters JIH is using, and none of those filters have "Current Project" in the "Select a project" dialog, then you should be fine with regards to #1.

      04-29-2016 11:45

      We are running on-premises so for 2 and 3 we would be ok.

      Now, for item 1.  I don't see the option "current project" listed. I do find a "Traditonal Project". Is this the project you are referring to?

      04-29-2016 08:31

      Hi Marc,
      I had a similar question regarding no 2 and 3 - as far as I understood this only applies to hosted customers.
      As far as no 1 goes I was assuming that you will need the check your filters in Jama that are being used in the hub.
      In Jama you can generate filters that use "current project" as filter criterium so that they can be used in all projects without having to change the scope of the filter each time. This must not be done for filters that are being used by the hub.
      So you would have to check all your filters in Jama that are being used by the hub if they use it. If they do you will have to change it to point to a dedicated project.

      Anna

      04-29-2016 08:22

      How can I check if the following conditions occur at our on-premises (JIH with JIRA setup) software?

      "-the “current project” scope in Jama filters is used to map between Jama and other tools

      -your organization uses OAuth to authenticate users

      -your organization uses SAML to authenticate users and plans to enable REST in the near future "

      04-26-2016 18:05

      I will keep you updated and may end up asking for you opinion if we need any help from a customer perspective.

      04-26-2016 10:54

      Thank you Kristina, I am highly interested in the results. We are currently affected by the lack of a compiled set of documentation that is useful for us - if it had been availalbe it would have saved time here and on your support side, I guess...

      04-25-2016 21:34

      Ooh, I'm glad you found that! We're actually working out the best way to future serve JIH users. There is a lot of documentation from Tasktop themselves, but given that not everything is applicable to JIH, we didn't think it made sense to use it all for Jama. Let me check in with someone else on this and get back to you.

      04-25-2016 11:08

      Thank you for that information, Kristina.

      Accidently I stumbled over "Known Limitations" chapters in the tasktop help today. There is at least some information we can start with:

      http://help.tasktop.com/help/index.jsp

      Search for "Known limitations". Do you now if the online-help is
      adapted?

      04-21-2016 15:58

      Ah, gotcha. I checked with Iris (since she's our JIH guru) and she doesn't have a list of known issues from Tasktop. She did point out there is one issue that you should know about. SOS-DEF-97/SOS-BUG-1081 "JIH versions 4.4+ replace the com.tasktop.artifacts.bridge upon restart, which allows plain text password in TRACE logging." There is a workaround, which is to delete the problem jar before enabling TRACE Logging. (found in C:\Users\<USERNAME>\AppData\Roaming\TasktopSync\workspace\\.metadata\.plugins\): delete com.tasktop.artifacts.bridge. You would have to delete this file every time you restart the JIH, too, as it gets repopulated.

      04-21-2016 06:52

      Hi Kristina,

      thanks for your clarification regarding LDAP - I understand now that as we are on-premise customers this should not be affecting us.

      The reaseon I was asking for the list of known issues is that we have to go through the validation process for use in regulated processes with the Jama Integration Hub soon and for OTS-software (=off-the-shelf) it is required to review the known issues list for the software under validation. If you don't have such a list - do you think this could be made available by tasktop?

      Anna

      04-20-2016 14:51

      Anna, good questions...
      1. The OAuth issue is mentioned because the JIH simply doesn't work with OAuth, which is required for our hosted customers who use the REST API and SAML...but SAML and LDAP are implemented differently in Jama, so I don't imagine there's a problem. I checked with Gustavo and Iris and they have heard of no LDAP/JIH issues.

      2. The issues posted up top are the only known issues at this time. (These release notes are a bit misleading—there are a bunch of fixes here implemented by Tasktop that were never reported to us by our customers, so I don't know that they were ever relevant.)

      04-20-2016 08:11

      Hi,
      as we are currently in the validation phase of the JIH I am considering the use the 4.5.7 version.
      There are a couple of questions though:

      - We use LDAP for registering our users - is that a problem (I am referring to the note that organizations using OAuth should not update to this version)

      - Is there a list with known issues of this version available?

      Thank you,
      Anna

      12-14-2015 23:22

      We have made available a new update for the JIH, available at http://www.jamasoftware.com/download-jih/. Check the Release Notes above to determine if you should upgrade. (Hint: you should if you use newer versions of JIRA.)

      11-24-2015 22:29

      Hey Barry! Thanks for pointing that out. It should be fixed now.

      11-24-2015 08:21

      Hi Kristina

      FYI, the JIH Configuration Considerations link on the download page appears to fail. http://downloads.jamasoftware.com/jih/jama-integration-hub-configuration-considerations-ds.pdf 

      11-23-2015 17:20

      Not a silly question! Previously we were disseminating the JIH on an individual scale. The download page just went live on Friday night: 
      http://www.jamasoftware.com/download-jih/

      11-23-2015 13:22

      Probably a silly question, but where do I download the latest version?

      11-02-2015 22:52

      Garn, we have tested and confirmed that Tasktop 4.3 can sync attachments provided your Jama environment has turned on the REST API. The REST API is available on hosted instances now and will be available for on-premises instances in early 2016.

      09-24-2015 22:39

      Garn, I don't have an official release date yet, but I'll be sure to respond to this when we do.

      09-15-2015 14:28

      Do we know when the ability to sync attachments with TFS will be released?

      08-28-2015 14:14

      Thanks for clarifying, Iris.

      08-26-2015 22:35

      Hi Ryan,

      You are correct in your assumption that the JIH 4.2 version will include the new features outlined in the previous Tasktop releases.

      To answer your question, it's a little bit of both functionality 1 and 2. While it would be cool to map the entire set of Requirements so both Text and Requirement items are synced with a single mapping, that is not currently possible. However, it is possible to create two separate Task Mappings using the same set. You would just configure both mappings to point to different items. In this case a mapping for Text items and a mapping for Requirements.

      So, synchronization of Text items does not have to come from a dedicated set of Text items, but you can not map all item types within a set to sync from a single Task Mapping.

      Hope that helps.

      Iris

      08-21-2015 17:23

      My understanding is that new versions of JIH pull in most/all of the changes in the Tasktop Sync versions which were released since the last JIH version.

      We were previously using JIH 4.04. Based on the generic release notes for Tasktop Sync 4.1, one of the new features in 4.1 is:
      • 25832 - Jama Text items can be synchronized
      I'm assuming that JIH 4.2 has picked this up as well. Can you clarify what limitations, if any, there are around this capability? I can't find any details in the JIH documentation.

      Specifically, does this new functionality permit:
      1. Synchronization of Text items only from a dedicated Set of Text items

        or

      2. Synchronization of Text items within a Task Mapping of another type of item (e.g. Text items interleaved in a Set of Requirement items, and both item types handled by the same Task Mapping)
      I'm assuming that it only provides support for #1, but thought I'd confirm, since #2 would be really cool. :)