Jama Integration Hub (JIH) Release Notes

By Jama posted 06-13-2015 00:31

  

Jama Integration Hub (JIH) UPGRADE VERSION 4.19.4

Published: 08/09/2019(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.

 

Upgrade Notes 

 Connector-Specific Upgrade Notes

General (Services)

      • 97693: The following Vendor repository versions are no longer available under Tasktop's general support. These versions are now available under extended support only:


        • Atlassian Jira (Software and Core) - 7.4 
        • Jira Service Desk - 3.4.x, 3.5.x, 3.6 
        • CA Agile Central (Rally) - 2017.1 
        • Micro Focus ALM - 11.5 (SP2) 
        • Micro Focus Dimensions RM - 12.5 
        • Planview Enterprise One - 14, 15 
        • VersionOne - 18.0 (Winter 2018), 18.1 (Spring 2018)

        Please reach out to your Tasktop contact if you are currently on one of the aforementioned versions and they will be able to guide you accordingly.

Atlassian Jira

      • 96286: State transitions involving the field "Sprint(s)" must be renamed to "Assigned Sprint".

BMC Remedy

      • 95314: Customers using the SOAP API to access Remedy should update their web service files to the latest as documented on the Remedy Connector Documentation page. Customers accessing Remedy through REST will not need to make any changes.

Micro Focus ALM Octane

    • 98018: It is recommended that the Shared Space Admin role is unassigned from the integration user to speed up the listing of workspaces when creating a new collection.

QASymphony qTest Manager

      • 95252: To resolve a performance issue, Tasktop may identify all items within QASymphony integration(s) as 'changed' and do a one-time synchronization upon upgrade.

Targetprocess

      • 94237: Type limitations set in Targetprocess for custom relationship fields are now enforced during integration. If users do, in fact, want types outside of those limitations to continue to synchronize, the limitations configured within Targetprocess must be expanded.

      • 95196: Mappings that write to the TestPlan field "LinkedBug" must be changed to write to the "LinkedGeneral" field instead.

Tricentis Tosca

    • 95131: Business Test Cases can no longer be created in Tosca via Tasktop integration.

Fixes

 

 

Sync Fixes

 

 

General

      • 95951: Fixed an issue where attachments deleted in the source repository were synced back from the target repository.

      • 94473: Fixed an issue where synchronization of two rich text fields resulted in a conflict.

Server

      • 96882: Upgraded H2 to 1.4.197, resolving an issue where daylight saving's time was being respected in timezones that do not have daylight saving's time, leading to mismatches between timestamps in the log files and timestamps in the UI.

      • 96720: Resolved an issue causing a background task to pop up the task list indexer dialog window.

      • 96516: Fixed an issue where a synchronization error could occur if a person was not found when using map by field. Behavior has been updated to use the default target person.

      • 96515: Resolved an issue where setting trace level logging did not set the logging level of the connectors.

      • 96282: Fixed an issue that caused duplicates due to Jira task ids not being upgraded.

Studio

    • 95702: Fixed an issue that occasionally resulted in incorrect page order in post-install wizard.

 

 

Connector-Specific Fixes

 

 

Atlassian Jira

      • 97214: Changed how connector handles HTML error deserialization. Complete HTML error pages will not be printed to the logs unless logging level threshold is set to DEBUG or lower.

      • 96899: Fixed an issue where inline code would come back from Jira with excessive @ symbols. Inline code should now maintain its structure when syncing back from Jira.

      • 96286: Fixed an issue where sprints were unable to be updated during state transitions.

      • 96014: Fixed an issue where sprints would appear as IDs instead of names when no boards were available.

      • 95082: Tasktop will set a default maximum length for Jira text fields if the associated credentials don’t have administrative rights to do so.

      • 97665: This restores person matching by email for artifacts synced into JIRA on-demand repositories, which was impacted by a recent Atlassian privacy change that hides user emails by default.

Blueprint

      • 96246: Fixed an issue causing an excessive number of 409 "conflict" responses in the logs.

BMC Remedy

      • 96397: Added a repository field for Remedy REST that ensures artifact location URI points to a valid location. Please see Connector Docs for configuration details.

      • 96329: Fixed an issue where the Remedy connector inaccurately reported an error with the message 'Unable to find metadata for field' when connecting via REST API.

      • 95673: Fixed an issue where the 'Approval Phase Name' field in the BMC Remedy connector was incorrectly set as writable. This field is now marked as read only.

CA Agile Central (Rally)

      • 96591: Fixed an issue where changesets failed to be created if they linked to the same artifact.

      • 95887: Fixed an issue where the HTTP client would fail to timeout when connecting via SSL.

IBM Rational DOORS Next Generation

      • 97498: Fixed an issue where work items with workflows were not being retrieved.

iRise

      • 96809: Fixed an issue where new artifacts or changes to iRise would not be synced if a mapped text field had more than 2000 characters.

Jama

      • 96909: Addressed an issue where Jama may fail to load projects due to a SOAP response when REST is configured on the repository.

      • 94951: Fixed an issue where synchronization may fail due to nested text blocks in a rich text field.

Micro Focus ALM Octane

      • 96910: Fixed an issue where synchronizations involving certain single select fields would fail.

      • 98018: The integration user is no longer required to have the Shared Space Admin role.

Microsoft Azure DevOps Server (TFS)

      • 97645: Fixed an issue where the Azure DevOps (TFS) connector did not identify the standard Resolved Resolution picklist field as a single select field.

      • 95233: Fixed an issue where the Azure DevOps (TFS) connector's rich text markup language name changed, leading to integration errors.

Planview LeanKit

      • 95361: Fixed an issue where mapping numeric fields in LeanKit could cause integration events to get stuck in 'processing.'

      • 95061: LeanKit connector will no longer display task types which are not also configured to be cards.

QASymphony qTest Manager

      • 95909: Fixed errors in QASymphony connector where potential changing of root module to project information on the server would require application restarts.

      • 95252: Fixed an issue where new custom fields added to the QASymphony UI could cause performance issues due to Tasktop erroneously detecting all artifacts as changed.

      • 94780: Details about the task id will now be visible in the Tasktop Sync error message if an artifact cannot be retrieved.

      • 97666: Fixed an issue which could cause the QASymphony qTest Manager connector to hang while performing creates or updates.

      • 97345: Fixed an issue where an artifact's revision would not be correct under some configurations, resulting in unnecessary synchronizations.

Salesforce

      • 95198: Fixed an issue where a newly added Salesforce field could cause an error.

      • 95197: "Modify All" and "View All" permissions are no longer required for the Tasktop user.

ServiceNow

      • 97344: Fixed an issue where Tasktop did not list single select field values if the field in ServiceNow had no dependent field specified, but did have options with dependent values.

      • 97128: Fixed an issue where ServiceNow returns an unencoded next-page URL during change detection which caused the connector to be unable to request the next page.

      • 97111: Fixed an issue where errors would occur due to insufficient permissions or an invalid user set as a person field on an artifact.

      • 96729: Fixed an issue where artifact retrieval failed if a dependent required field was empty.

      • 96680: Fixed an issue where empty attachments caused parsing errors during artifact retrieval.

      • 95385: ServiceNow 'priority' field on incidents is no longer assumed to be read only.

      • 97878: Fixed an issue where certain artifact filtering conditions produced an error during change detection.
      • 97708: Fixed an issue that occurred when retrieving artifacts with catalog variables with duplicated variable names.

      • 97707: Fixed an issue where ServiceNow could return a 400 error when retrieving artifacts with a large number of catalog variables

Targetprocess

      • 97133: Fixed an issue where having a custom field called 'Type' in TargetProcess would cause integrations to fail.

      • 94760: Fixed an issue where some artifacts with custom links could not be retrieved.

      • 94237: Fixed an issue where type limitations set in Targetprocess for custom relationship fields were not enforced, allowing relationships to ineligible types to synchronize to Targetprocess.

Tricentis Tosca

      • 95131: Fixed an issue where unsupported Business Test Cases could be created in Tosca via integration.

VersionOne

    • 96066: Reduced Tasktop load on VersionOne by making change detection improvements.

Features

 

 

Sync Features

 

 

Bridge

      • 95563: Previously, when an artifact had a relationship (link) to another artifact in a project that was inaccessible, it blocked the entire artifact from synchronizing. This fix skips the inaccessible relationship (link) and continues to synchronize the rest of the artifact when "validate links before synchronizing" is checked when using the TaskLink to TaskLink caster.

General

    • 92383: Users can now map Tosca test case test folder attributes to ALM test subject attributes.

Connector-Specific Features

 

 

Atlassian Jira

      • 96701: Atlassian Crowd enabled SSO authentication is now supported for Jira.

      • 96186: Added support for Jira Service Desk version 4.2.

      • 96184: Added support for Jira Core and Jira Software version 8.2.

      • 94509: Added support for Jira Service Desk 4.1.

      • 92858: Added support for Jira Service Desk version 4.0.

      • 88266: Added support for Jira Data Center. Please see connector docs for configuration details.

Blueprint

      • 95625: Added support for Blueprint 10.1 (with Storyteller 4.1).

BMC Remedy

      • 97115: Reduces change detection paging size to reduce payload retrieved and thus load on the server.

      • 97065: Added support for the use of Smart IT URLs for the artifact location field in Remedy. Please see Connector Docs for configuration details.

      • 96058: An integration with BMC Remedy Change artifacts using the REST API no longer requires customization of the Change Interface form.

      • 95715: Comments that are submitted via e-mail will no longer be excluded from synchronization. Users may see old e-mail generated comments synchronize if other integration-triggering changes are made to the artifacts that contain them.

      • 95322: Field names in Tasktop will now match the field names in the Remedy UI, rather than the database names for each field. Note that this applies to Remedy version 18.08 or higher, and requires a REST API connection. See Connector Documentation for further information.

      • 95314: Added read-only support for InstanceId and Submitter fields on Remedy Change and Problem artifacts.

      • 94819: Support for REST has been added to the BMC Remedy Connector. In order to connect to a Remedy repository using a REST API instead of SOAP API, 'Use REST API' must be checked on the repository connection screen. Please refer to connector documentation for further information.

      • 93355: Added support for BMC Remedy version 19.02.

      • 91126: Tasks are now supported as a work item. See Connector Docs for more information.

CA PPM

      • 93621: Added support for CA PPM version 15.6.

GitHub Issues

      • 95129: Added support for Personal Access Token authentication.

IBM Rational Team Concert

      • 95534: The IBM Rational Team Concert connector provides an authenticator for Kerberos/SPNEGO SSO.

iRise

      • 94695: The iRise connector now references a newly added field property to determine whether a field is read-only or not.

Jama

      • 96510: Added support for Jama Connect version 8.38.

Micro Focus ALM Octane

      • 96289: Added support for Micro Focus ALM Octane version 12.60.47.

Micro Focus PPM

      • 96396: Added support for Micro Focus PPM version 9.53.

Planview Enterprise

      • 97019: The Worklog Submission Status field is now optional for setting up a repository connection.

      • 95427: Planview worklogs can now be submitted with either "Approved" or "Entered" status.

QASymphony qTest Manager

      • 95632: Added support for QASymphony qTest Manager version 9.6.1.

SmartBear QAComplete

      • 96890: Added support for Smartbear QAComplete version 12.20.

      • 96288: Added support for Smartbear QAComplete version 12.14.

      • 95633: Added support for Smartbear QAComplete version 12.13.

Targetprocess

      • 95196: TestPlan now links to types besides Bug by using the new "LinkedGeneral" field.

Tricentis Tosca

      • 96182: Added support for Tricentis Tosca version 12.2.

      • 92896: Added support for Tricentis Tosca version 12.1.

      • 90149: Added Support for Tricentis Tosca version 12.0.

VersionOne

    • 95634: Added support for VersionOne Spring 2019.


Jama Integration Hub (JIH) UPGRADE VERSION 4.18.11

Published: 07/10/2019(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.

 

Upgrade Notes

Connector-Specific Upgrade Notes

Atlassian Jira

  • 96286: State transitions involving the field "Sprint(s)" must be renamed to "Assigned Sprint".

Features

Sync Features

General

  • 92383: Users can now map Tosca test case test folder attributes to ALM test subject attributes.

Features

Connector-Specific Features

BMC Remedy

  • 95322: Field names in Tasktop will now match the field names in the Remedy UI, rather than the database names for each field. Note that this applies to Remedy version 18.08 or higher, and requires a REST API connection. See Connector Documentation for further information.

Fixes

Sync Fixes

General

  • 95951: Fixed an issue where attachments deleted in the source repository were synced back from the target repository.

 

Server

  • 96516: In some cases, a person not found, when using map by field, resulted in a synchronization error. Changed this to fall back to default target person.
  • 96515: Resolved an issue where setting trace level logging did not set the logging level of the connectors.
  • 92924: Added better handling for task id changes during upgrade to reduce the chance of upgrade errors.
  • 96882: Upgraded H2 to 1.4.197, resolving an issue where daylight saving's time was being respected in timezones that do not have daylight saving's time, leading to mismatches between timestamps in the log files and timestamps in the UI.
  • 96720: Resolved an issue causing a background task to pop up the task list indexer dialog window.
  • 96282: Fixed an issue that caused duplicates due to Jira task ids not being upgraded.

Studio

  • 95702: Fixed an issue that occasionally resulted in incorrect page order in post-install wizard.

 

Connector-Specific Fixes

 

Atlassian Jira

  • 96286: Fixed an issue where sprints were unable to be updated during state transitions.
  • 96014: Fixed an issue where sprints would appear as IDs instead of names when no boards were available.

 

BMC Remedy

  • 96329: Fixed an issue where the Remedy connector inaccurately reported an error with the message 'Unable to find metadata for field' when connecting via REST API.
  • 96397: Added a repository field for Remedy REST that ensures artifact location URI points to a valid location. Please see Connector Docs for configuration details.

Blueprint

  • 96246: Fixed an issue where changes were often discarded before retrieving unchanged artifacts.
  • 96246: Fixed an issue causing an excessive number of 409 "conflict" responses in the logs.

iRise

  • 96809: Fixed an issue where new artifacts or changes to iRise would not be synced if a mapped text field had more than 2000 characters.

ServiceNow

  • 96729: Fixed an issue where artifact retrieval failed if a dependent required field was empty.

 

Planview LeanKit

  • 95361: Fixed an issue where mapping numeric fields in LeanKit could cause integration events to get stuck in 'processing.'

QASymphony qTest Manager

  • 95909: Fixed errors in QaSymphony connector where potential changing of root module to project information on the server would require application restarts.

ServiceNow

  • 96246: Fixed an issue where changes were often discarded before retrieving unchanged artifacts.
  • 95385: ServiceNow 'priority' field on incidents is no longer assumed to be read only.

 

VersionOne

  • 96066: Reduced Tasktop load on VersionOne by making change detection improvements.


Jama Integration Hub (JIH) UPGRADE VERSION 4.18.3

Published: 04/30/2019 (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.

LATEST MAJOR UPDATE was 4.18.1 which included Jira8 support and much more.
This update is in feature Parity with TIH 19.2.3

    • Upgrade Notes
      • Connector-Specific Upgrade Notes
        • Micro Focus ALM
        • QASymphony qTest Manager
    • Fixes
      • Connector-Specific Fixes
        • Atlassian Jira
        • Microsoft Azure DevOps Server (TFS)
        • Planview LeanKit
        • QASymphony qTest Manager
        • Salesforce
        • Targetprocess
    • Features
      • Connector-Specific Features
        • BMC Remedy

    Upgrade Notes

    Connector-Specific Upgrade Notes

    Micro Focus ALM

      • 95158: Removed support for ALM 14.0x-SaaS (Patch 2)

    QASymphony qTest Manager

      • 95252: To resolve a performance issue, Tasktop may identify all items within QASymphony integration(s) as 'changed' and do a one-time synchronization upon upgrade.

    Fixes

    Connector-Specific Fixes

    Atlassian Jira

      • 95082: Tasktop will set a default maximum length for Jira text fields if the associated credentials don’t have administrative rights to do so.

    Microsoft Azure DevOps Server (TFS)

      • 95233: Fixed an issue where the Azure DevOps (TFS) connector's rich text metadata changed leading to integration errors.

    Planview LeanKit

      • 95061: LeanKit connector will no longer display Task types which are not also configured to be Cards.

    QASymphony qTest Manager

      • 95252: Fixed an issue where new custom fields added to the QASymphony UI could cause performance issues due to Tasktop erroneously detecting all artifacts as changed.

      • 94780: Details about the artifact handle will now be visible in the Tasktop error message if an artifact cannot be retrieved.

    Salesforce

      • 95197: "Modify All" and "View All" permissions are no longer required for the Tasktop user.

    Targetprocess

      • 94760: Fixed an issue where some artifacts with custom links could not be retrieved.

    Features

    Connector-Specific Features

    BMC Remedy

      • 94819: Support for REST has been added to the BMC Remedy Connector. In order to connect to a Remedy repository using a REST API instead of SOAP API, 'Use REST API' must be checked on the repository connection screen. Please refer to connector documentation for further information.


Jama Integration Hub (JIH) UPGRADE VERSION 4.18.1

Published: 04/30/2019 (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.

Tasktop Sync Release Notes - 4.18.1

  • Upgrade Notes
    • Connector-Specific Upgrade Notes
      General
      Atlassian Jira
      BMC Remedy
      Micro Focus ALM
      Micro Focus ALM Octane
      QASymphony qTest Manager
  • Fixes
    • Sync Fixes
      General
      Server
      Studio
      Web UI
    • Connector-Specific Fixes
      Atlassian Jira
      BMC Remedy
      CA Agile Central (Rally)
      GitHub Issues
      IBM Rational DOORS
      IBM Rational Team Concert
      iRise
      Jama
      Micro Focus ALM
      Micro Focus ALM Octane
      Micro Focus PPM
      Microsoft Azure DevOps Server (TFS)
      Microsoft Project Server
      Microsoft Sharepoint
      Pivotal Tracker
      QASymphony qTest Manager
      Salesforce
      Targetprocess
      Tricentis Tosca
  • Features
    • Sync Features
      General
      Studio
    • Connector-Specific Features
      Atlassian Jira
      Blueprint
      BMC Remedy
      CA PPM
      IBM Rational Team Concert
      iRise
      Jama
      Micro Focus ALM
      Micro Focus ALM Octane
      Micro Focus Dimensions RM
      Micro Focus PPM
      Micro Focus Solutions Business Manager
      Microsoft Azure DevOps Server (TFS)
      Microsoft Project Server
      Pivotal Tracker
      Planview Enterprise
      QASymphony qTest Manager
      ServiceNow
      SmartBear QAComplete
      Targetprocess
      Tricentis Tosca
      VersionOne
      Zendesk

Upgrade Notes

Connector-Specific Upgrade Notes

General

  • The following vendor repository versions are no longer available under Tasktop's general support. These versions are now available under extended support only: 
    • CA Agile Central (Rally) - 2014.1, 2014.2, 2014.3, 2015.1, 2015.2, 2016.1 
    • CA PPM - 15.1 
    • IBM Rational DOORS Next Generation (IBM RRC) - 5.0, 5.0.1, 5.0.2 
    • IBM Rational Quality Manager - 5.0, 5.0.1, 5.0.2 
    • IBM Rational Team Concert - 5.0, 5.0.1, 5.0.2 
    • Jama Connect - 8.0, 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 8.11, 8.12, 8.13, 8.14 
    • Micro Focus Dimensions RM - 12.1.1, 12.2, 12.2.1, 12.3, 12.4, 12.4.1 
    • Micro Focus Solutions Business Manager - 10.1.3, 10.1.4, 10.1.4.1, 10.1.5, 10.1.5.1, 10.1.5.2 
    • ServiceNow: Service Desk, Agile Development, PPM - Jakarta 
    • VersionOne - 17.3 (Fall 2017) 

Please reach out to your Tasktop contact if you are currently on one of the aforementioned versions and they will be able to guide you accordingly.

Atlassian Jira

    • 91557: 
      • If you are integrating Zephyr Cloud artifacts, you must upgrade to a version of Tasktop with these changes to prevent existing integrations from being disrupted. Zephyr On Premise is not impacted. 
      • The user account associated with the Jira Cloud connection must have the 'browse users and groups' permission granted. 
      • The auto-comment user name will need to be manually changed to accountid for any existing and new Zephyr Cloud mappings. By default, Sync is using the username from repository settings as auto-comment user when creating new mappings. If repository settings do not specify username (for example, when email + API token authentication is used), the auto-comment user field will be empty. In either case, in order to be used by Sync, it will need to be replaced with a valid accountid. Behavior for Zephyr On Premise is unchanged. 
      • Any task mappings for Zephyr Cloud that map person attributes may no longer work. A person-mapping.xml file may be required. Behavior for Zephyr On Premise is unchanged. 
      • All usernames in the person-mapping.xml files related to Zephyr Cloud mappings will need to be replaced with Jira accountIDs. Behavior for Zephyr On Premise is unchanged. 
      • Any existing person-mapping.xml files with field-based person mapping using Jira Cloud’s person-id or person-username fields will no longer work. These will need to be changed to use a different Jira person field, such as person-email. Behavior for Zephyr On Premise is unchanged. 
      • The mapping scripts will be passed the Jira accountID as an argument when mapping Jira Cloud users, and will need to be updated accordingly. Behavior for Zephyr On Premise is unchanged. 
      • If there are field mappings that map Jira Cloud person fields to a string field, be aware that those will now flow the Jira account ID (i.e. an alphanumeric string such as 'abc-123-def-456'), rather than the Jira username (a readable field such as ‘TasktopUser’). A custom caster script can be used to flow the display name to a string field. Behavior for Zephyr On Premise is unchanged.

    • 89282: • If you are integrating Jira Cloud artifacts, you must upgrade to a version of Tasktop with these changes to prevent existing integrations from being disrupted. Jira On Premise is not impacted.

      • If you are integrating Zephyr Cloud artifacts, do not yet upgrade to this version of Tasktop (or any later versions), as changes in this version will disrupt existing Zephyr integrations. Zephyr on Premise is not impacted.

      • The user account associated with the Jira cloud connection must have the 'browse users and groups' permission granted.

      • The auto-comment username will need to be manually changed to accountid for any existing and new Jira Cloud mappings. By default, Sync is using the username from repository settings as auto-comment user when creating new mappings. If repository settings do not specify username (for example, when email + API token authentication is used), the auto-comment user field will be empty. In either case, in order to be used by Sync, it must be replaced with a valid accountid. Behavior for Jira On Premise is unchanged.

      • Any task mappings for Jira Cloud that map person attributes without using a person-mapping.xml file will no longer work. A person-mapping.xml file will be required. Behavior for Jira On Premise is unchanged.

      • All usernames in the person-mapping.xml files related to Jira Cloud mappings must be replaced with Jira accountIDs. Behavior for Jira On Premise is unchanged.

      • Any existing person-mapping.xml files with field-based person mapping using Jira Cloud’s person-id or person-username fields will no longer work. These must be changed to use a different Jira person field, such as person-email. Behavior for Jira On Premise is unchanged.

      • The mapping scripts will be passed the Jira accountID as an argument when mapping Jira Cloud users, and will need to be updated accordingly. Behavior for Jira On Premise is unchanged.

      • If there are field mappings that map Jira Cloud person fields to a string field, be aware that those will now flow the Jira account ID (i.e. an alphanumeric string such as 'abc-123-def-456'), rather than the Jira username (a readable field such as 'TasktopUser'). A custom caster script can be used to flow the display name to a string field. Behavior for Jira On Premise is unchanged.

BMC Remedy

    • 92679: Customers will need to update their custom web services files (available in the Connector Docs) to ensure that performance when retrieving persons from the repository is not negatively affected.

    • 91172: The Phone_Number field on Incidents has been renamed to Customer_Phone_Number on the version 6.2 Incident form. When the new form is installed on the BMC Remedy server, the Phone_Number field will need to be re-mapped to Customer_Phone_Number in any integrations containing the field.

Micro Focus ALM

    • 91733: Options mappings by id of the Subject field on Tests need to be remapped upon upgrade.

Micro Focus ALM Octane

    • 91002: If you are using private fields in your Octane integrations, please contact Tasktop support to ensure existing integrations are not disrupted upon upgrade.

    • 93561: If you are using the Application Modules field on Run entities in your Octane integrations, please contact Tasktop support to ensure existing integrations are not disrupted upon upgrade.

QASymphony qTest Manager

    • 91446: To prevent possible upgrade issues, stop all QASymphony task mappings and end all user sessions for the configured QASymphony repository user before upgrading Tasktop.

Fixes

Sync Fixes

General

    • 91160: Fixed an issue where the wrong error message was displayed when a user was not found.

    • 94438: Added support for non-US ASCII characters in email address' display names.

Server

    • 94233: Fixed an issue where the incorrect error message was displayed when an option for a single-select field was not found.

    • 91654: Fixed a rare issue that caused excessive CPU utilization in long-running Sync processes.

Studio

    • 91258: Fixed an issue that prevented users from exporting state from Tasktop Sync to import into Tasktop Integration Hub if mapping's name contained special characters.

Web UI

    • 94553: Fixed an issue with rendering ALM secure artifact links in Web UI.

Connector-Specific Fixes

Atlassian Jira

    • 93670: Fixed an issue where multiple retries of certain operations were causing slower performance of Jira on premise integrations.

    • 93456: Fixed an issue that could occur when creating a query in Jira if the artifact type has an 'Epic Link' field.

    • 92690: Fixed an error that prevented synchronization of Jira issues with Epic links.

    • 91982: Fixed an error that occurred when trying to save a Jira query due to a misconfigured Service Desk plugin.

BMC Remedy

    • 92679: Made optimizations to the BMC Remedy connector to improve retrieving large number of persons.

    • 92243: Made optimizations in the BMC Remedy connector to improve searching over large queries.

    • 90964: Fixed a bug in the BMC Remedy connector where attempts to update an artifact could fail when that artifact had a field with a user that could not be validated.

CA Agile Central (Rally)

    • 93772: Daylight savings time hour offsets properly accounted for when handling planned dates.

GitHub Issues

    • 94772: Fixed an issue with the GitHub connector where it could fail to link an Issue to a Milestone.

    • 92481: Fixed an issue where the Github connector was unable to create Milestones against github.com.

IBM Rational DOORS

    • 92455: Fixed an issue where requirements with an empty object text could not be synchronized.

    • 92137: Fixed an issue where the IBM Rational DOORS connector could wait indefinitely for an operation to complete.

    • 91662: Fixed an issue where unsupported custom module only attributes would show up as available attributes for DOORS mappings.

    • 76576: Fixed an issue where the wrong error was displayed after failing to find an attachment for a DOORS object.

IBM Rational Team Concert

    • 94400: Fixed an issue where comments that exceeded the size limit for the RTC web UI attempted to flow to RTC, causing the web UI to break. RTC now correctly sets a maximum comment size and Sync will throw an error instead of writing comments that are too long to RTC.

    • 92610: Fixed an issue where large attachments would fail to synchronize from IBM RTC to another repository.

iRise

    • 94231: Fixed an iRise REST API issue where custom fields were cleared when non-custom fields were updated by Tasktop.

    • 48559: iRise chapters' changes are now detected when any summary, content or id attributes are changed.

Jama

    • 93605: Fixed an issue where an artifact's parent was updated erroneously.

Micro Focus ALM

    • 92449: Fixed an issue where authentication failed when using Ping Federate authentication on ALM SaaS repositories.

    • 79313: Micro Focus ALM server shutdown is now recognized and any operation failing during the shutdown will be retried.

    • 79028: Fixed an issue where "available memory in resource pool" server errors were not retried.

Micro Focus ALM Octane

    • 93561: The Application Modules field is no longer exposed in the schema for Run entities.

    • 91285: Fixed an issue that prevented the Micro Focus ALM Octane connector from connecting to the server.

    • 91002: Fixed the Micro Focus ALM Octane connector to avoid exposing private fields for use in integrations.

Micro Focus PPM

    • 91880: Fixed an issue where an empty date value on the PPM artifact could cause an error and prevent synchronization.

Microsoft Azure DevOps Server (TFS)

    • 94542: Fixed an issue where the connector did not always return all allowed or suggested values for a picklist field.

    • 94258: Fixed an issue where updating an artifact with several relationship values could remove more relationships than expected.

    • 93590: Fixed an issue where the connector would fail to retrieve a work item if that work item or one of its comments referenced a user that did not have a unique display name.

    • 93295: Fixed an issue where the connector did not delete a potentially stale local cache of metadata from the server, leading to potential synchronization errors.

    • 91714: Fixed an issue where some updates failed when links were removed and link comments were updated at the same time.

    • 91555: Fixed an error that occurred when retrieving an artifact with multiple '#' symbols in its URI fields.

    • 91529: Fixed an error encountered when synchronizing Double, Long, or Boolean values in certain locales.

    • 91528: Fixed an issue where links were not properly added to work items.

    • 91264: Fixed an issue where the connector failed to return comments associated with a work item.

    • 91051: Fixed an issue where discovering options for picklist fields could take a long time.

    • 91050: Fixed an issue where errors were sometimes improperly handled in localized Azure DevOps/TFS installations. This change enables the connector to correctly detect, classify, and handle Azure DevOps/TFS REST error responses, regardless of the initial install language.

Microsoft Project Server

    • 92244: A detailed authentication failure message is provided when users apply invalid credentials for Microsoft Sharepoint or Microsoft Project Server.

Microsoft Sharepoint

    • 92244: A detailed authentication failure message is provided when users apply invalid credentials for Microsoft Sharepoint or Microsoft Project Server.

Pivotal Tracker

    • 94773: If an artifact is referencing a deactivated user, the integration will no longer error out.

QASymphony qTest Manager

    • 93972: Fixed an error that occurred after setting a QASymphony single-select field to an inactive option.

    • 91446: Fixed an issue where an error could occur on Tasktop upgrade if token expiry was more than several minutes.

Salesforce

    • 93065: Fixed an issue where artifacts without a name would cause an error when appearing in search results.

    • 91589: Fixed an issue where schema retrieval failed due to validation on string fields with a maximum length of zero.

Targetprocess

    • 92222: Targetprocess person search was updated to only return Users and Requesters. A "Kind" field was added to Targetprocess persons to distinguish Users from Requesters.

Tricentis Tosca

    • 91833: In Tosca, custom ‘date’ fields are referenced in the UI, but truly behave as string fields. This fixes an issue where custom date fields were inadvertently not supported due to not being properly treated as strings.

Features

Sync Features

General

    • 93964: References to Microsoft Team Foundation Server connector renamed Microsoft Azure DevOps Server (TFS) due to company rebranding.

Studio

    • 91397: All repositories using legacy connectors will be upgraded during the Post Installation Wizard.

Connector-Specific Features

Atlassian Jira

    • 94502: Added support for Jira version 8.1.

    • 92937: Zephyr Test Execution Attachment notes can now flow as Attachment Description to other tools (if supported there).

    • 92127: Required change for Atlassian GDPR change for Jira cloud. Handles new Jira cloud response header parameter X-AACCOUNTID to be able to differentiate anonymous vs. non-anonymous responses. This will replace X-AUSERNAME which will disappear after the Atlassian deprecation period.

    • 91557: The 'username' field has been replaced by the 'account ID' field (an alphanumeric string such as 'abc-123-def-456') for Atlassian Jira and Zephyr Cloud to fulfill the requirements of GDPR. Please see upgrade notes for details on what this means for integrations. The behavior for on-premise instances of Jira and Zephyr is unchanged.

    • 89282: Due to GDPR changes made by Atlassian, the 'username' field (i.e. 'TasktopUser') has been replaced by the 'account ID' field (an alphanumeric string such as 'abc-123-def-456') for Jira Cloud and Zephyr Cloud. Please see upgrade notes for details on integration consequences. Behavior for Jira/Zephyr On Prem is unchanged.

    • 87046: Added support for Jira version 8.0.

Blueprint

    • 92420: Added support for Blueprint 10.0 (with Storyteller 4.0).

BMC Remedy

    • 93816: Added support for InstanceId and Submitter fields for Incidents. Customers will need to update their custom web services files (available in the Connector Docs) to synchronize InstanceId and Submitter fields for Incidents.

    • 92902: Attachments flowing into BMC Remedy will now result in the WorkInfo note showing the filename. This will make it easier to find an attachment (especially when multiple attachments are referred to in the description).

    • 91172: Customer First Name, Customer Last Name, Customer Phone Number, and Customer Email fields are now supported on Incidents as read-only fields. Contact First Name, Contact Last Name, Contact Phone Number, and Contact Email are now supported on Incidents and Work Orders as read-only fields. To synchronize the new fields, the version 6.2 forms (or later) must be installed on the BMC Remedy server. For details, please see Tasktop connector documentation (https://docs.tasktop.com/tasktop/connector-documentation ).

    • 87936: Remedy version 18 up to version 18.08.01 is now supported. Customers must re-download the latest version of the custom web services available on Connector Documentation for Remedy 18 support.

CA PPM

    • 92133: The CA PPM Connector now only lists artifact types and fields that have the corresponding NSQL queries on the server. Refer to the Connector Docs for the list of required NSQL queries.

    • 90859: Added support for CA PPM version 15.5.1.

IBM Rational Team Concert

    • 92096: Added support for the Subscribed By field.

    • 90202: Added support for Wiki type fields as RichText fields.

iRise

    • 32668: iRise connector can now support search by user name, display name, first name, last name, and email address.

Jama

    • 94871: Added support for Jama Connect version 8.36.

    • 94431: 'Jama' connector rebranded as 'Jama Connect'.

Micro Focus ALM

    • 94197: 'Micro Focus ALM (HPE)' connector rebranded as 'Micro Focus ALM.'

    • 94189: Micro Focus ALM 14.01 (SaaS) is now supported. API Key Authentication is now supported on Micro Focus ALM 14.01 (SaaS).

    • 94048: Added support for a much wider range of characters in attachment and web link names (including unicode characters).

    • 93134: Micro Focus ALM Test Instances are now contained within Test Sets.

    • 92237: API Key Authentication is now supported on ALM On Premise version 12.60.

    • 92035: Added support for Micro Focus ALM/QC version 14 Patch 2.

    • 91713: Micro Focus (HPE) ALM Test Folders are now supported as an artifact type.

    • 90198: State transitions are now supported for Micro Focus ALM (HPE) Defect status field.

Micro Focus ALM Octane

    • 94198: 'Micro Focus ALM Octane (HPE)' connector rebranded as 'Micro Focus ALM Octane'.

    • 93774: Added support for Micro Focus ALM Octane version 12.60.35.

Micro Focus Dimensions RM

    • 94187: 'Dimensions RM' connector rebranded as 'Micro Focus Dimensions RM.'

    • 93158: Added support for Dimensions RM (Serena) version 12.6.2.

Micro Focus PPM

    • 94188: 'Micro Focus PPM (HPE)' connector rebranded as 'Micro Focus PPM.'

    • 93354: Added support for Micro Focus PPM version 9.52.

    • 90523: Added support for Micro Focus PPM version 9.51.

    • 83866: Added support for Micro Focus PPM version 9.50.

Micro Focus Solutions Business Manager

    • 94196: 'Solutions Business Manager' connector rebranded to 'Micro Focus Solutions Business Manager' and logo updated.

    • 91651: Added support for Micro Focus Solutions Business Manager version 11.5.

Microsoft Azure DevOps Server (TFS)

    • 94037: Added support for Microsoft Azure DevOps Server version 2019.

    • 93077: 'Microsoft Team Foundation Server' connector rebranded as 'Microsoft Azure DevOps Server (TFS).'

    • 91650: Added support for Azure DevOps Server (formerly Microsoft TFS) version 2019 RC1.

Microsoft Project Server

    • 92100: Added support for Actual Start and Actual Finish attributes.

    • 90418: The predecessor field is now supported as a multi-valued artifact type.

    • 90009: Added support for Microsoft Project Server version 2019.

Pivotal Tracker

    • 92936: Tasktop will no longer flow comments that are auto-created due to attachment creation.

Planview Enterprise

    • 94713: Planview connector supports worklogs, effort, and assignees fields on the PPL level.

    • 88938: Added support for Planview Enterprise One release 17.

QASymphony qTest Manager

    • 94504: Added support for QASymphony qTest Manager version 9.6.

    • 93328: Added support for QASymphony qTest Manager version 9.5.3.

ServiceNow

    • 92230: Added support for ServiceNow Madrid.

SmartBear QAComplete

    • 94505: Added support for SmartBear QAComplete version 12.12.

    • 93773: Added support for Smartbear QAComplete version 12.11.

    • 93353: Added support for Smartbear QAComplete version 12.1.

    • 92074: Added support for SmartBear QAComplete version 12.0.

Targetprocess

    • 93906: Targetprocess connector now supports Portfolio Epics.

Tricentis Tosca

    • 94315: The Test Case field on Execution Entry artifact now uses the Test Case smart field in the model mapping. The Execution Entry field on Execution Test Case Log artifact now uses the TEST_EXECUTION smart field in the model mapping

VersionOne

    • 92422: Added support for VersionOne Winter 2019 (19.0)

Zendesk

    • 92935: Tasktop will no longer flow comments that are auto-created due to attachment creation.


Jama Integration Hub (JIH) UPGRADE VERSION 4.17.12

Published: 04/02/2019 (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.


Jama Integration Hub/Tasktop Sync Release Notes - 4.17.12


Jama Integration Hub Fixes and Features

    • General
    • Studio

Connector-Specific Fixes

    • Atlassian Jira (REST)
    • BMC Remedy
    • CA Agile Central (Rally)
    • IBM Rational DOORS
    • IBM Rational Team Concert
    • Jama
    • Micro Focus ALM (HPE)
    • Microsoft Team Foundation Server
    • Salesforce
    • ServiceNow
    • Targetprocess

Connector-Specific Upgrade Note

    • Atlassian Jira (REST)
    • BMC Remedy

Jama Integration Hub Fixes and Features

General

* 91160: Fixed an issue where the wrong error message was displayed when a user was not found

Studio

* 91397: All repositories using legacy connectors will be upgraded during the Post Installation Wizard.

Connector-Specific Fixes

Atlassian Jira (REST)
* 93670: Fixed an issue where multiple retries of certain operations were causing slower performance of Jira on premise integrations.
* 92690: Fixed an error that prevented synchronization of Jira issues with Epic links.

BMC Remedy
* 92679: Made optimizations to the BMC Remedy connector to improve retrieving large number of persons.
* 90964: Fixed a bug in the BMC Remedy connector where attempts to update an artifact could fail when that artifact had a field with a user that could not be validated.
* 87936: Remedy version 18 up to version 18.08.01 is now supported. Customers must re-download the latest version of the custom web services available on Connector Documentation for Remedy 18 support.
* 92243: Made optimizations in the BMC Remedy connector to improve searching over large queries.

CA Agile Central (Rally)
* 93772: Daylight savings time hour offsets properly accounted for when handling planned dates.

IBM Rational DOORS
* 91662: Fixed an issue where unsupported custom module only attributes would show up as available attributes for DOORS mappings.
* 92455: Fixed an issue where requirements with an empty object text could not be synchronized.

IBM Rational Team Concert
* 92610: Fixed an issue where large attachments would fail to synchronize from IBM RTC to another repository.

Jama
* 93605: Fixed an issue where an artifact's parent was updated erroneously.

Micro Focus ALM (HPE)
* 92449: Fixed an issue where authentication failed when using Ping Federate authentication on ALM SaaS repositories.

Microsoft Team Foundation Server
* 91051: Fixed an issue where discovering options for picklist fields could take a long time.
* 93590: Fixed an issue where the TFS connector would fail to retrieve a work item if that work item or one of its comments referenced a user that did not have a unique display name.
* 91050: Fixed an issue where errors were sometimes improperly handled in localized TFS installations. This change enables the TFS connector to correctly detect, classify, and handle TFS REST error responses, regardless of the initial install language.

Salesforce
* 93065: Fixed an issue where artifacts without a name would cause an error when appearing in search results.

ServiceNow
* 92230: Added support for ServiceNow Madrid.

Targetprocess
* 92222: Targetprocess person search was updated to only return Users and Requesters. A "Kind" field was added to Targetprocess persons to distinguish Users from Requesters.

Upgrade Notes

Connector-Specific Upgrade Notes

Atlassian Jira (REST)
* 91557: If you are integrating Zephyr Cloud artifacts, you must upgrade to a version of Tasktop with these changes to prevent existing integrations from being disrupted. Zephyr On Premise is not impacted. 

 The user account associated with the Jira Cloud connection must have the 'browse users and groups' permission granted. 

 The auto-comment user name will need to be manually changed to accountid for any existing and new Zephyr Cloud mappings. By default, Sync is using the username from repository settings as auto-comment user when creating new mappings. If repository settings do not specify username (for example, when email + API token authentication is used), the auto-comment user field will be empty. In either case, in order to be used by Sync, it will need to be replaced with a valid accountid. Behavior for Zephyr On Premise is unchanged. 

 Any task mappings for Zephyr Cloud that map person attributes without using a person-mapping.xml file will no longer work. A person-mapping.xml file will be required. Behavior for Zephyr On Premise is unchanged. 

 All usernames in the person-mapping.xml files related to Zephyr Cloud mappings will need to be replaced with Jira accountIDs. Behavior for Zephyr On Premise is unchanged. 

 Any existing person-mapping.xml files with field-based person mapping using Jira Cloud’s person-id or person-username fields will no longer work. These will need to be changed to use a different Jira person field, such as person-email. Behavior for Zephyr On Premise is unchanged. 

 The mapping scripts will be passed the Jira accountID as an argument when mapping Jira Cloud users, and will need to be updated accordingly. Behavior for Zephyr On Premise is unchanged. 

 If there are field mappings that map Jira Cloud person fields to a string field, be aware that those will now flow the Jira account ID (i.e. an alphanumeric string such as 'abc-123-def-456'), rather than the Jira username (a readable field such as ‘TasktopUser’). A custom caster script can be used to flow the display name to a string field. Behavior for Zephyr On Premise is unchanged.

BMC Remedy
* 92679: Customers will need to update their custom web services files (available in the Connector Docs) to ensure that performance when retrieving persons from the repository is not negatively affected.


Jama Integration Hub (JIH) UPGRADE VERSION 4.17.4

Published: 02/04/2019 (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.

Fixes

Connector-Specific Fixes

Atlassian Jira (REST)

    • 91982: Fixed an error that occurred when trying to save a Jira query due to a misconfigured Service Desk plugin.

    • 92127: Required change for Atlassian GDPR change for Jira cloud. Handles new Jira cloud response header parameter X-AACCOUNTID to be able to differentiate anonymous vs. non-anonymous responses. This will replace X-AUSERNAME which will disappear after the Atlassian deprecation period.

Microsoft Project Server

    • 92244: A detailed authentication failure message is provided when users apply invalid credentials for Microsoft Sharepoint or Microsoft Project Server.

Microsoft Sharepoint

    • 92244: A detailed authentication failure message is provided when users apply invalid credentials for Microsoft Sharepoint or Microsoft Project Server.


Jama Integration Hub (JIH) UPGRADE VERSION 4.17.2

Published: 01/22/2019 (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.

Upgrade Notes

Sync Upgrade Notes

Bridge

      • 88631: Errors related to ListFieldOptionsOperation may be reported as a part of migration, but are expected and will not impact the upgrade.

Studio

    • 89936: All repositories using legacy connectors will be upgraded during the Post Installation Wizard.

    • 89764: Customers will need to perform a schema refresh on all repositories.

Connector-Specific Upgrade Notes

General

  • The following Vendor repository versions are no longer available under Tasktop's general support. These versions are now available under extended support only: 

    Atlassian Jira (Software & Core) versions: 7.2, 7.3
    Atlassian Jira Service Desk 3.2, 3.3
    Tricentis Tosca 10.1, 10.2

    Please reach out to your Tasktop contact if you are currently on one of the aforementioned versions and they will be able to guide you accordingly.

Atlassian Jira (REST)

      • 89437: Support for Jira Service Desk versions 3.1 and prior have been removed as these versions have reached End of Life by the vendor. Tasktop recommends users check that they are on a supported version of this 3rd party product before upgrading.

      • 84674: • If you are integrating Jira Cloud artifacts, you must upgrade to a version of Tasktop with these changes to prevent existing integrations from being disrupted. Jira On Premise is not impacted.

        • If you are integrating Zephyr Cloud artifacts, do not yet upgrade to this version of Tasktop (or any later versions), as changes in this version will disrupt existing Zephyr integrations. Zephyr on Premise is not impacted.

        • The user account associated with the Jira cloud connection must have the 'browse users and groups' permission granted.

        • The auto-comment username will need to be manually changed to accountid for any existing and new Jira Cloud mappings. By default, Sync is using the username from repository settings as auto-comment user when creating new mappings. If repository settings do not specify username (for example, when email + API token authentication is used), the auto-comment user field will be empty. In either case, in order to be used by Sync, it must be replaced with a valid accountid. Behavior for Jira On Premise is unchanged.

        • Any task mappings for Jira Cloud that map person attributes without using a person-mapping.xml file will no longer work. A person-mapping.xml file will be required. Behavior for Jira On Premise is unchanged.

        • All usernames in the person-mapping.xml files related to Jira Cloud mappings must be replaced with Jira accountIDs. Behavior for Jira On Premise is unchanged.

        • Any existing person-mapping.xml files with field-based person mapping using Jira Cloud’s person-id or person-username fields will no longer work. These must be changed to use a different Jira person field, such as person-email. Behavior for Jira On Premise is unchanged.

        • The mapping scripts will be passed the Jira accountID as an argument when mapping Jira Cloud users, and will need to be updated accordingly. Behavior for Jira On Premise is unchanged.

        • If there are field mappings that map Jira Cloud person fields to a string field, be aware that those will now flow the Jira account ID (i.e. an alphanumeric string such as 'abc-123-def-456'), rather than the Jira username (a readable field such as 'TasktopUser'). A custom caster script can be used to flow the display name to a string field. Behavior for Jira On Premise is unchanged.

Blueprint

      • 89438: Support for Blueprint versions 6.4 and prior have been removed as these versions have reached End of Life by the vendor. Tasktop recommends users check that they are on a supported version of this 3rd party product before upgrading.

Dimensions RM (Serena)

      • 89442: Support for Micro Focus Dimensions RM (SDRM) version 12.1.0.4 has been removed as this version has reached End of Life by the vendor. Tasktop recommends users check that they are on a supported version of this 3rd party product before upgrading.

IBM Rational Team Concert

      • 89910: Any existing mapping for fields of type 'Team Area List', 'Project Area List', or 'Process Area List' will need to be re-mapped in order to take advantage of the new writable status of these fields.

Micro Focus ALM Octane (HPE)

      • 88973: The Application Modules multi select field needs to be re-mapped as its options have been renamed to include the full path of the application module.

Planview Enterprise

      • 88780: The Planview Person fields have been updated to exclude the "person-id" field as these fields held identical values to the "person-username" field. If Person Reconciliation makes use of extension scripts, all references of "person-id" should be replaced with "person-username".

QASymphony qTest Manager

      • 91446: To prevent possible upgrade issues, stop all QASymphony integrations and end all user sessions for the configured QASymphony repository user before upgrading Tasktop.

Salesforce

      • 89691: Salesforce fields of type URI (except the read-only "URL" field) are now of type String. Mappings that include these fields will need to be updated by removing the fields and adding them again.

VersionOne

    • 89443: Support for VersionOne versions 17.2 (Summer 2017) and prior have been removed as these versions have reached End of Life by the vendor. Tasktop recommends users check that they are on a supported version of this 3rd party product before upgrading.

Fixes

Sync Fixes

Bridge

      • 89979: Fixed an issue where the TaskAttribute.getOptions() method was not returning correct information for multiple-select fields.

General

      • 76905: Added a configurable option to process artifacts if the proxy task does not belong to the current task mapping. If this option is disabled, proxy tasks will be validated against the task mapping and will not be processed if they do not belong to it. The option is enabled by default.

Server

      • 91654: Fixed a rare issue that caused excessive CPU utilization in long-running Sync processes.

      • 89552: Fixed an issue with Change Repository URL wizard layout.

      • 85337: Added support for long file names to prevent FileNotFoundException while synchronizing some TFS repositories.

Studio

      • 91258: Fixed an issue that prevented users from exporting state from Tasktop Sync to import into Tasktop Integration Hub if mapping's name contained special characters.

      • 89764: Added an empty option to value mapping caster for multi-select fields.

Web UI

    • 90885: Web UI now sets Strict-Transport-Security HTTP header for secure connections.

Connector-Specific Fixes

Atlassian Jira (REST)

      • 91139: Fixed an error that prevented the retrieval of an item due to the board having no columns mapped.

      • 89978: Fixed an issue where Jira could cause extra traffic during change detection when no changes had occurred.

      • 89408: Fixed an issue where not all field values were shown by Tasktop on the field mapping screen.

      • 88972: Fixed an error where a cascading dependent field would not be found in the schema when moving a Jira item to a closed state.

      • 88860: Fixed a performance issue in the Jira connector that pertains to synchronizing the Test Cycle artifact from the Zephyr Cloud plugin.

      • 88799: Fixed a 'redefining field template' error by filtering out duplicates when a customer configuration contains fields with the same metadata for sd-request-participants in Jira.

      • 88539: To prevent 400 errors, HTTP 400 responses for anonymous requests that are not the login URL will now trigger an authentication request from the product.

      • 88203: Fixed an issue involving the synchronization of rich text fields in Jira where quoting multi-line markup wasn't being transformed to HTML correctly.

BMC Remedy

      • 90552: Fixed an issue where person entries in Remedy without associated login names could cause integrations to fail. Such entries will now be ignored by Tasktop.

Blueprint

      • 88623: Fixed an issue where a certain character from a Blueprint rich text field would appear as a question mark when synchronized.

CA Agile Central (Rally)

      • 89514: Fixed an issue where person search in CA Agile Central (Rally) was slow when there were many users.

GitHub Issues

      • 89094: Fixed an issue where Tasktop could not retrieve linked Milestones due to a SaaS API change in GitHub.

IBM Rational ClearQuest

      • 89134: Fixed an issue where fields with names starting with a digit would cause XML parsing errors during artifact retrieval. These fields will now be ignored and not be considered part of the artifact.

      • 89027: Fixed an issue where ClearQuest queries with a very large set of artifacts could negatively impact change detection performance.

IBM Rational DOORS

      • 89551: Fixed issue where locked DOORS Objects were not being filtered out from searches.

IBM Rational Team Concert

      • 90761: Fixed an issue that prevented users from synchronizing attachments to RTC 5 & 6 if the attachment filenames contained characters such as '#' that were considered invalid in RTC 4.

      • 88993: Fixed an issue where RTC 6.0.1 and later could not properly sync String List fields on creation.

Jama

      • 89766: Fixed an issue where the HTTP Method PUT was being requested instead of PATCH for updating artifacts.

Micro Focus ALM (HPE)

      • 89459: Fixed an issue where a large number of release cycles could cause a "FULL head" error, blocking integration with Test Sets.

      • 80169: Fixed an issue where insufficient permissions could be incorrectly identified as expired authentication state.

      • 79313: Micro Focus ALM server shutdown is now recognized and any operation failing during the shutdown will be retried.

      • 79111: Micro Focus ALM server startup is now recognized and any operation failing during the startup will be retried.

      • 79028: Fixed an issue where "available memory in resource pool" server errors were not retried.

      • 68725: Improved error handling of Micro Focus (HPE) ALM Favorites Search.

Micro Focus ALM Octane (HPE)

      • 91285: Fixed an issue that prevented the Micro Focus ALM Octane connector from connecting to the server.

      • 90903: Fixed an issue where the Micro Focus ALM Octane connector exposed an unsupported field from Micro Focus ALM Octane, causing 'HTTP 404 not found' errors.

      • 90026: Fixed an issue where projects could not be retrieved when a user did not have elevated permissions on Shared Spaces.

      • 88076: Fixed an issue where synchronizing unsupported file types in to Octane could block the integration.

Micro Focus PPM (HPE)

      • 91880: Fixed an issue where an empty date value on the PPM artifact could cause an error and prevent synchronization.

Microsoft Team Foundation Server

      • 91714: Fixed an issue where some updates failed when links were removed and link comments were updated at the same time.

      • 91555: Fixed an error that occurred when retrieving an artifact with multiple '#' symbols in its URI fields.

      • 91529: Fixed an error encountered when synchronizing Double, Long, or Boolean values in certain locales.

      • 91528: Fixed an issue where links were not properly added to work items.

      • 91264: Fixed an issue where the Microsoft Team Foundation Server connector failed to return comments associated with a work item.

      • 89553: Fixed an issue where the TFS connector was unable to successfully get team project collection metadata from the server.

      • 88509: Fixed an issue where Azure DevOps collections couldn't be created with the new 'dev.azure.com' URL.

Planview LeanKit

      • 61030: Fixed an issue where underline was lost in rich text synchronization from LeanKit Html to Jira Confluence.

QASymphony qTest Manager

      • 91446: Fixed an issue where an error could occur on Tasktop upgrade if token expiry was more than several minutes.

      • 90902: QASymphony qTest Manager defects can now have a description field with unlimited content size.

Salesforce

      • 91589: Fixed an issue where schema retrieval failed due to validation on string fields with a maximum length of zero.

      • 89722: Fixed an issue where multi-links were unnecessarily being retrieved, thus using up too many Salesforce pagination cursors and resulting in INVALID_QUERY_LOCATOR errors.

      • 89691: URI fields are now treated as Strings by the connector to prevent errors/exceptions thrown when a non-URI value is set for URI fields.

      • 89574: Fixed an issue where Salesforce configurations were blocked in Tasktop due to per-field permissions on picklist fields.

      • 89233: Fixed issue where repository URI wasn't normalized prior to authentication.

ServiceNow

      • 89392: Fixed an issue where ServiceNow collection search was resulting in 'pagination not supported' errors and silently failing.

      • 89203: Fixed an issue in the ServiceNow connector where an attachment with an empty filename disabled all attachment synchronization. Now, users with the right permission can attach files with empty filenames, and synchronize the attachments.

Tricentis Tosca

    • 91833: In Tosca, custom ‘date’ fields are referenced in the UI, but truly behave as string fields. This fixes an issue where custom date fields were inadvertently not supported due to not being properly treated as strings.

    • 88688: Fixed an issue where Test Mandate Entries and Business Execution Lists could not be retrieved.

Features

Sync Features

General

    • 90435: The error report can now include repository metadata if provided by the connector.

Connector-Specific Features

Atlassian Jira (REST)

      • 90548: Added support for Jira Service Desk version 3.16.

      • 90547: Added support for Jira version 7.13.

      • 90297: Added support for Zephyr version 4.0.

      • 90296: Added support for Zephyr version 3.6.

      • 90295: Added support for Zephyr version 3.5.

      • 89483: Added support for Jira Service Desk version 3.15.

      • 89482: Added support for Jira Service Desk version 3.14.

      • 89481: Added support for Jira Service Desk version 3.13.

      • 89480: Added support for Jira Service Desk version 3.12.

      • 89479: Added support for Jira Service Desk version 3.11.

BMC Remedy

      • 90962: Vendor Ticket Number on Work Orders is now supported. To synchronize the Vendor Ticket Number field on Work Orders, Tasktop's Work Order form version 6.1 (or later) must be installed on the BMC Remedy server. For details, please see Tasktop connector documentation (https://docs.tasktop.com/tasktop/connector-documentation ).

      • 91172: Customer First Name, Customer Last Name, Customer Phone Number, and Customer Email fields are now supported on Incidents as read-only fields. Contact First Name, Contact Last Name, Contact Phone Number, and Contact Email are now supported on Incidents and Work Orders as read-only fields. To synchronize the new fields, the version 6.2 (or later) forms must be installed on the BMC Remedy server. For details, please see Tasktop connector documentation (https://docs.tasktop.com/tasktop/connector-documentation  ).
      • 90391: Added support for BMC Remedy version 9.1.03 and 9.1.04.

CA PPM

      • 90859: Added support for CA PPM version 15.5.1.

      • 86565: Added support for Risk, Change Request, and Issue as work items to the CA PPM Connector. In order to enable support for these work item types, the corresponding NSQL scripts should be installed from the Connector Docs.

Dimensions RM (Serena)

      • 89364: Added support for Dimensions RM version 12.6.1.

      • 89363: Added support for Dimensions RM version 12.6.

      • 89362: Added support for Dimensions RM version 12.5.1.

IBM Rational Team Concert

      • 90202: Added support for Wiki type fields as RichText fields.

      • 89910: Added support to enable updating and mapping field values for custom fields of type 'Team Project List', 'Team Area List', and 'Team Process List.'

      • 88966: Contributor List type fields are now supported on RTC.

Jama

      • 89270: Added support for Jama version 8.31.

      • 89005: The 'Links' widget is now supported for Jama.

Micro Focus ALM (HPE)

      • 90247: Read-only support for a "Test Configs" relationships field on Tests, a "Test Runs" relationships field on Test Configs, a "Test Config" relationship field on Test Instances, and an "Executed" date field on Test Runs has been implemented.

      • 90198: State transitions are now supported for Micro Focus ALM (HPE) Defect status field.

Micro Focus ALM Octane (HPE)

      • 88973: Application Modules are now labeled with their full path rather than just their name.

      • 88806: Added support for "Requirements" field on Defects and Features. Added support for "Covered requirement" field on Tests.

Microsoft Project Server

      • 90418: The predecessor field is now supported as a multi-valued artifact type.

Microsoft Sharepoint

      • 90007: Added support for Microsoft Sharepoint version 2019.

Planview Enterprise

      • 90512: The "Detailed" field is now supported for all artifacts below the Primary Planning Level. This field indicates whether or not an artifact has children. It is implemented as a read-only String field, and can take on values "Y" or "N".

      • 88780: Removed Planview Person ID field because it contained the same value as Planview Person Username.

      • 88653: Added support for multi-select fields.

      • 86028: Added support for Planview Enterprise One version 16.

QASymphony qTest Manager

      • 89942: Added support for QASymphony qTest Manager version 9.3.

      • 85188: Added support for QASymphony qTest Manager version 9.1.5.

Salesforce

      • 88985: Salesforce Files are retrieved as attachments, and attachments are now created in Salesforce as Salesforce Files. The legacy Salesforce Attachment type still gets retrieved.

ServiceNow

      • 89524: Logo updated for 'ServiceNow' connector.

SmartBear QAComplete

      • 89268: Added support for SmartBeart QAComplete version 11.9.

Solutions Business Manager (Serena)

      • 89361: Added support for Solutions Business Manager version 11.4.1.

      • 86485: Added support for Solutions Business Manager version 11.4.

Sparx Systems Enterprise Architect

      • 88594: Added support for Sparx Enterprise Architect version 14.1.

      • 81180: Added support for Sparx Enterprise Architect version 14.

Targetprocess

      • 91012: Users can now flow Targetprocess Releases in integrations.

VersionOne

    • 90263: Added support for VersionOne version 18.3 (Fall 2018).


Jama Integration Hub (JIH) UPGRADE VERSION 4.16.8

Published: 11/28/2018 (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 general fixes across connectors

Upgrade Notes

Connector-Specific Upgrade Notes

Salesforce

  • 89691: Salesforce fields of type URI (except the read-only "URL" field) are now of type String. Mappings that include these fields will need to be updated.


Features since JIH 4.16.3

General Features

 Bridge

  • 89979: Fixed an issue where the TaskAttribute.getOptions() method was not returning correct information for multiple-select fields.
  • 76905: Added a configurable option to process artifacts if the proxy task does not belong to the current task mapping. If this option is disabled, proxy tasks will be validated against the task mapping and will not be processed if they do not belong to it. The option is enabled by default.

 Server

  • 89552: Fixed the issue with Change Repository URL wizard layout.

 

Connector-Specific Fixes

Atlassian Jira (REST)

  • 89978: Fixed an issue where Jira could cause extra traffic during change detection when no changes have happened.
  • 89408: Fixed an issue where a limited amount of group options was being shown in the Jira Connector. Now all group options are visible.
  • 88972: Fixed an error where a cascading dependent field would not be found in the schema when moving a JIRA item to a closed state.
  • 88203: Fixed an issue involving the synchronization of rich text fields in Jira where quoting multi-line markup wasn't being transformed to html correctly.

 

CA Agile Central (Rally)

  • 89514: Fixed an issue where the person search in CA Agile Central (Rally) was slow when there were many users.

Micro Focus ALM (HPE)

  • 89459: Fixed an issue where a large number of release cycles could cause a "FULL head" error, blocking integration with Test Sets.

Micro Focus ALM Octane (HPE)

  • 90026: Fixed an issue where projects could not be listed when a user did not have elevated permissions on Shared Spaces.
  • 88076: Fixed an issue where synchronizing unsupported file types in to Octane could block the integration.

Salesforce

  • 89574: Fixed an issue where the Salesforce Sales Cloud connector attempted to process a picklist field that the user does not have access to.

ServiceNow

  • 89203: Fixed an issue in the ServiceNow connector where an attachment with an empty filename disabled all attachment synchronization. Now, users with the right permission can attach files with empty filenames, and synchronize the attachments.


Jama Integration Hub (JIH) UPGRADE VERSION 4.16.3

Published: 9/19/2018 (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 general fixes across connectors and support for new 

Features since JIH 4.15.11

General Features

Bridge

  • Added support of a new method for connectors communicating retriable errors when artifacts or other required resources are locked.

Server

  • Added performance improvements and minor UI enhancements.

Connector-Specific Features

Atlassian Jira

CA Agile Central (Rally)

    • Added support for CA Agile Central version 2018.1.

Microsoft Team Foundation Server

    • Added support for Microsoft TFS version 2018.3.

VersionOne

    • Added support for VersionOne 18.2 (Summer 2018).

    • Connector now supports Rollup Categories as a read-only single-select field on Defects, Stories, and Epics.

    • Logo updated for 'VersionOne' connector.

Fixes since JIH 4.15.11

General Fixes

ALM Systems

    • The upgrade produces handle that include project, type, test plan ID, test suite ID, and test run ID.

Bridge

    • Fixed "No non-null value found for variable" issue that blocked the synchronization of Jira items.

    • Fixed "No non-null value found for variable" issue that blocked schema generation for Jira.

General

    • Added a configurable option to only email the most recent errors (up to 100) since the last notification job run. If this option is selected, the email will include a link to view all errors in Web UI.

    • Added a configurable option to only process artifacts if the proxy tasks belong to the current task mapping. If this option is disabled, proxy tasks will be validated against the task mapping and will not be processed if they do not belong to it.

Server

    • When conflicting attribute value is modified by a script, Tasktop now logs the value produced by the script as incoming value.

    • Added support for long file names to prevent FileNotFoundException while synchronizing some TFS repositories.

 

Connector-Specific Fixes

Atlassian Jira

    • Fixed a performance issue in the Jira connector that pertains to synchronizing the Test Cycle artifact from the Zephyr Cloud plugin.

    • If a customer configuration contains duplicate fields with the same metadata for sd-request-participants in Jira, connector will filter out duplicates.

    • HTTP 400 responses for anonymous requests that are not the login URL will trigger an authentication request from the product.

    • Fixed an issue where Jira integrations could not perform state transitions involving either Original Estimate or Remaining Estimate.

    • Fixed an issue where attachment synchronization from Jira was failing for attachments with .htm or .html extension.

    • Fixed an issue where some Jira synchronizations were failing temporarily with an error message of 'Issue not found.'

    • Fixed an issue in the Jira connector where repository proxy settings, if configured, were not being used when the authentication method 'Authentication Chain: Basic Authentication with Two Way SSL' was selected.

    • Fixed an issue where connector will filter out duplicate fields from a customer configuration containing the same metadata for sd-request-participants in Jira.

HP QC / ALM 

    • Fixed an issue where the HP QC/ALM (Mylyn) connector would incorrectly report a failure and block synchronization when an artifact checkout was rolled back on ALM 12.01 or later.

Jama

    • Fixed an issue where attachments without a specified size couldn't be synchronized into Jama.

    • Fixed an issue with the Jama connector where users were unable to flow artifacts with embedded attachments if the file name contained spaces or special characters.

    • Tables in Jama are created with a border and left-aligned text.

Microsoft Team Foundation Server

    • Fixes an issue where a connection is reset while listing options.

    • Fixed issue where Azure DevOps collections couldn't be created with the new 'dev.azure.com' URL.

    • Fixed an issue where not all projects are listed when there are a large number of projects on the server.

    • Fixed an issue where admin-level permissions were required to use TFS connector.

    • Product now retries operations when the TFS error "Too many concurrent users are getting metadata incremental" happens.

Upgrade Notes

Sync Upgrade Notes

  • Errors related to ListFieldOptionsOperation may be reported as a part of migration, but are expected and will not impact the upgrade.

Connector-Specific Upgrade Notes

General

    • The following Vendor repository versions are no longer available under Tasktop's general support. These versions are now available under extended support only: 

      Atlassian Jira (Software & Core) versions: 6.4, 7.0, 7.1 
      BMC Remedy versions: 8.1.01, 8.1.02 
      Jama version: 2015.5 
      Micro Focus ALM / QC versions: 11.5 (SP2), 12 (SP1) 
      Solutions Business Manager version: 10.1.2 
      Microsoft TFS versions: 2012, 2012.1, 2012.2, 2012.3, 2012.4 
      Planview Enterprise versions: 11.3, 13 
      Thoughtworks Mingle versions: 13.1, 13.2, 13.3, 13.4, 14.1, 14.2, 15.1, 15.2, 16.1, 16.2 
      Tricentis Tosca versions: 9.1, 9.2, 9.3, 10.0 

      Please reach out to your Jama Software contact if you are currently on one of the aforementioned versions and they will be able to guide you accordingly.

Atlassian Jira

    • Attachments on Test Execution are no longer detected on normal change detection. To ensure these updates synchronize, a full scan must occur or another qualifying change must be made to the artifact.

    • Atlassian will be deprecating basic authentication with passwords and cookie-based authentication for Jira Cloud by December 1, 2018. Users must configure a Tasktop repository authentication method other than 'Standard Authentication,' such as 'Email Address and API Token Authentication (Jira Cloud only),' by that time. See Atlassian notice here: https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/ .


Jama Integration Hub (JIH) UPGRADE VERSION 4.15.11

Published: 9/19/2018 (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 general fixes across.

Features since JIH 4.15.5

  • Added performance improvements and minor UI enhancements.

Fixes since JIH 4.15.5

General Fixes

  • Fixed "No non-null value found for variable" issue that blocked the synchronization of Jira items.
  • Fixed minor UI issue.

Connector-Specific Fixes

HP QC / ALM (OTA/REST)
  • Fixed an issue where the HP QC/ALM (Mylyn) connector would incorrectly report a failure and block synchronization when an artifact checkout was rolled back on ALM 12.01 or later.


Jama Integration Hub (JIH) UPGRADE VERSION 4.15.5

Published: 2018/07/09 (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 across connectors.

Features since JIH 4.14.15

  • Removed -canUpgradeLegacyConnectors startup argument and check for canUpgrade property during upgrade process.

Connector-Specific Features

Atlassian Jira (REST)

  • Added support for Jira Software and Jira Core version 7.10.
  • A new authentication method, 'Authentication Chain: Basic Authentication with Two Way SSL' was added to the Jira connector to support authentication chaining between two-way SSL and basic authentication.
  • Assignee field can now be written to, even when it is only editable in the Jira UI by using the 'Assign' or 'Assign to me' button.
  • Added support for Jira Software and Jira Core version 7.9.

Jama

  • Added support for Jama version 8.25.

Microsoft Team Foundation Server

  • The TFS SDK and CLC libraries used by the TFS connector were upgraded from 14.120.0 to 14.1340.0.
  • Added support for TFS version 2017 update 3.1.

VersionOne

  • Added support for VersionOne 18.1 (Spring 2018).
  • Logo updated for 'VersionOne' connector.

Fixes since JIH 4.14.15

General Fixes

  • Added a configurable option to only email the most recent errors (up to 100) since the last notification job run. If this option is selected, the email will include a link to view all errors in Web UI.
  • When conflicting attribute value is modified by a script, Tasktop now logs the value produced by the script as incoming value.
  • Fixed a rare issue with migration of artifact handles with obsolete required field values.
  • Fixed an issue that caused previous revisions of edited comments to be synchronized back as new comments after HP ALM upgrade.
  • Fixed an issue where Sync exported task URL instead of serialized identifier for tasks exported without state.
  • Fixed an issue where mapping by labels wasn't possible for dependent fields.
  • Improved Sync startup time for very large task lists.
  • Fixed an issue with display of empty information boxes in Sync Web UI.
  • Fixed Web UI issue where user could not log in without "Remember me" option selected.
  • When conflicting attribute value is modified by a script, Tasktop now logs the value produced by the script as incoming value.
  • Fixed an issue where Sync exported task URL instead of serialized identifier for tasks exported without state.

 

Connector-Specific Fixes

Atlassian Jira (REST)

  • Fixed an issue where attachment synchronization from Jira was failing for attachments with .htm or .html extension.
  • Fixed an issue where some Jira synchronizations were failing temporarily with an error message of 'Issue not found.'
  • Fixed an issue in Jira that caused 'connection pool shutdown' errors to appear.

  • Fixed an issue where users would see an "Unable to parse response" error when creating a Jira TaskRepository.

  • Fixed an issue with listing Sprint options on Jira work items when Scrum and Kanban boards exist within the same project.

  • Fixed an issue where a missing epic link caused an error in the Jira connector.

  • Fixed an issue where synchronizing artifacts with unexpected values in the watchers field caused an error.

  • Fixed an issue where repository URLs ending with '/' caused an error during synchronization.

  • Fixed an issue encountered when processing large amounts of content within Jira table cells.

  • Fixed an issue in the Jira connector where repository proxy settings, if configured, were not being used when the authentication method 'Authentication Chain: Basic Authentication with Two Way SSL' was selected.
  • Fixed an issue where attachment synchronization from Jira was failing for attachments with .htm or .html extension.
  • Added new authentication method, 'Email Address and API Token Authentication (Jira Cloud only),' as per Atlassian notice https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/ .
  • Fixed an issue where some Jira synchronizations were failing temporarily with an error message of 'Issue not found.'
  • Fixed an issue in Jira that caused 'connection pool shutdown' errors to appear.

CA Agile Central (Rally)

  • Connector can parse HTML in successful response messages.
  • Improved CA Agile Central error messages for better readability.

Jama

  • Fixed an issue with the Jama connector where users were unable to flow artifacts with embedded attachments if the file name contained spaces or special characters.
  • Fixed an issue where Jama connector would overwrite changes made to artifact in a separate, more recent change.

  • Fixed version detection against Jama cloud instance.

  • Fixed an issue in Jama that would prevent synchronization due to users that don't have a display name.

  • Jama connector now allows a greater range of unicode characters in Jama attachment file names.

  • Fixed an issue with the Jama connector where users were unable to flow artifacts with embedded attachments if the file name contained spaces or special characters.

Microsoft Team Foundation Server

  • Improved the error message for scenarios where Tasktop attempts to retrieve an artifact from a TFS project collection that has been closed (stopped).
  • Fixed an issue where retrieving too many query results would hit a limit. 

Upgrade Notes

Microsoft Team Foundation Server

  • Customers will need to download and install the TFS SDK and CLC 14.134.0 libraries to replace version 14.120.0 libraries.

Atlassian Jira (REST)



Jama Integration Hub (JIH) UPGRADE VERSION 4.14.17

Published: 2018/07/09 

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 fixes for Jira.

Fixes since JIH 4.14.15

General Fixes

  • Fixed an issue where Sync exported task URL instead of serialized identifier for tasks exported without state.

Connector-Specific Fixes

Atlassian Jira (REST)

  • Fixed an issue in Jira that caused 'connection pool shutdown' errors to appear.

 


Jama Integration Hub (JIH) UPGRADE VERSION 4.14.15

Published: 2018/06/20

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 fixes for Jira and Jama.

Fixes since JIH 4.14.11

General Fixes

  • Fixed an issue that caused previous revisions of edited comments to be synchronized back as new comments after HP ALM upgrade.

Connector-Specific Fixes

Atlassian Jira (REST)

  • Fixed an issue where users would see an "Unable to parse response" error when creating a Jira repository connection.

Jama

  • Fixed an issue where Jama connector would overwrite changes made to artifact in a separate, more recent change.


Jama Integration Hub (JIH) UPGRADE VERSION 4.14.11

Published: 2018/05/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 minor fixes for Jira, CA Agile and Jama.

Fixes since JIH 4.14.2

General Fixes

  • Fixed a rare issue with migration of artifact handles with obsolete required field values.
  • Fixed an issue with the display of empty information boxes in Sync Web UI.

Connector-Specific Fixes

Atlassian Jira

  • Fixed an issue where a missing epic link caused an error in the Jira connector.
  • Fixed an issue encountered when processing large amounts of content within Jira table cells.

CA Agile Central (Rally)

  • Connector can parse HTML in successful response messages.

Jama

  • Improvements to Jama text item integrations
  • Fixed version detection against Jama cloud instance.
  • Jama connector now allows a greater range of unicode characters in Jama attachment file names.

Jama Integration Hub (JIH) UPGRADE VERSION 4.14.2

Published: 2018/05/02 

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.

Fixes since JIH 4.13.19

General Fixes

  • Proxy Association Export Wizard now validates if Person Handles are valid on the tasks to be exported.
  • Upgraded Jetty web server used by the Tasktop Sync web container to version 9.2.13

Connector-Specific Fixes

Atlassian Jira

  • Fixed an issue where the Jira connector could not properly retrieve translated issues.
  • Tasktop now handles synchronizing collections with reference to deleted users more efficiently.
  • Fixed an issue where users were unable to create a new Jira repository connection due to attachment configuration.
  • Fixed an issue where rich text was converted incorrectly when flowing to Jira.
  • Fixed a deserialization error for repositories with Enhancer Plugin installed.
  • Fixed an issue in Jira where users with certain scripted fields were unable to create a collection.
  • Fixed an issue where special characters were incorrectly transformed during rich text transformations.
  • Fixed an issue causing degraded performance while synchronizing the Test Case artifact on Jira Cloud.
  • Fixed an issue with mapping a Jira nFeed field in a collection.
  • Fixed an issue where synchronizing artifacts with unexpected values in the watchers field caused an error.
  • Fixed an issue where repository locations ending with '/' caused an error during synchronization.

CA Agile Central (Rally)

  • Fixed an issue in the CA Agile Central connector where updating more than 25 comments or artifact links in one operation resulted in an server error.

Jama

  • Fixed an issue that prevented synchronization with certain versions of Jama.

Microsoft TFS

  • 81750: Improved the error message for scenarios where Tasktop attempts to retrieve an artifact from a TFS project collection that has been closed (stopped).
  • Test Case 'Steps' field is now a read-only string field.
  • Tasktop will now set a display name when a person is not found in order to prevent the “Person must have a display name” error.
  • Improved the Microsoft Team Foundation Server connector to better handle irregular person field values on work items.
  • Fixed an issue where modifying a Microsoft TFS project name could lead to HTTP errors.
  • Fixed an issue where unexpected user values returned from the TFS server were blocking Tasktop from running.
  • Updated the way TFS Git link URIs are handled in order to accommodate Git branches and tags with slashes in their names.
  • Fixed an issue where modifying a Microsoft TFS collection name could lead to HTTP errors.
  • Fixed the Microsoft Team Foundation Server connector to raise a more appropriate error when attempting to retrieve an artifact from a Team Project Collection that has been stopped.

VersionOne

  • Fixed an issue where an invalid web link value (e.g. one with spaces in the URI) could cause artifact retrieval to fail. These values are now being ignored.

Features since JIH 4.13.19

Atlassian Jira (REST)

  • Added support for Jira version 7.8.
  • Person reconciliation with email addresses for Jira is no longer case sensitive.
  • Added support for Jira Core.
  • OAuth 1.0a authentication is now supported for the Jira repository.
  • Custom multi-person fields, such as User Picker (multiple users), are now supported in Jira.
  • Jira connector no longer gives warnings about deprecated Atlassian token header when creating attachments.

CA Agile Central (Rally)

  • CA Agile Central connector now supports API Key authentication.
  • Improved performance for CA Agile Central artifact filtering based on fields LastRun, AcceptedDate, ActualStartDate, CloseDate, and LateChild Count.
  • Improved performance for artifact filtering by a number of CA Agile Central fields, including read-only and required fields.
  • Improved performance for artifact filtering utilizing nested sub-expressions such as "(x AND (y OR z))."
  • Improved performance for artifact filtering in CA Agile Central.
  • Added support for CA Agile Central version 2017.1.

Jama

  • Jama connector can now flow embedded images to rich text fields and comment fields for select target repositories. Please see Jama connector documentation for details and limitations.

Microsoft TFS

  • Added support for Microsoft TFS version 2018.1.
  • Support added for rich text tables.
  • Boolean fields (both out-of-the-box and custom) are now supported for VSTS and TFS 2017.2 and later.
  • Authentication via Personal Access Token to Microsoft Team Foundation Server and Microsoft Visual Studio Team Services is now properly supported.

VersionOne

  • Added support for VersionOne Winter 2018 (18.0).

Upgrade Notes

General Upgrade Notes

  • Configuration of Apache commons-logging via command line is no longer available. Customers can use log4j.xml for this purpose. 

Connector-Specific Upgrade Notes

CA Agile Central (Rally)

  • Users authenticating with an API Key will need to switch to the new "API Key Access" authentication option.
  • Improved CA Agile Central error messages for better readability.

Jama

  • Fixed an issue in Jama that would prevent synchronization due to users that don't have a display name.

Microsoft TFS

  • If a user saved a Personal Access Token in a previous version of Tasktop Sync, the token must be reentered after the product upgrade has completed. The user must choose Personal Access Token authentication from the repository settings and then enter the value of the token into the associating field.


Jama Integration Hub (JIH) UPGRADE VERSION 4.13.19

Published: 2018/04/16 

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 fixes.

Fixes since JIH 4.13.13

General Fixes

  • Modified the Support and Usage Report creation process to eliminate certain information from user-generated reports.

Connector-Specific Fixes

Atlassian Jira (REST)

  • Handle synchronizing collections with reference to deleted users more efficiently.

CA Agile Central (Rally)

  • 80892: Fixed an issue in the CA Agile Central connector where updating more than 25 comments or artifact links in one operation results in an server error.

Jama

  • Fixed an issue in Jama that would prevent synchronization due to users that don't have a display name.
  • Jama connector now allows a greater range of unicode characters in Jama attachment file names.

Microsoft TFS

  • Test Case ‘Steps’ field is now a read-only string field.
  • Fixes an error about display name occurring when a user cannot be retrieved from TFS by the connector.

 

Upgrade Notes

  • Configuration of Apache commons-logging via command line is no longer available. Customers can use log4j.xml for this purpose.


Jama Integration Hub (JIH) UPGRADE VERSION 4.13.3

Published: 2018/03/13 (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.

Features since 4.13.3

General Features

  • Includes support bundle improvements.

CA Agile Central (Rally)

  • CA Agile Central connector now supports API Key authentication.

 

Fixes since JIH 4.13.3

General Fixes

  • Proxy Association Export Wizard now validates if Person Handles are valid on the tasks to be exported.

Connector-Specific Fixes

Atlassian Jira

  • Fixed an issue where rich text was converted incorrectly when flowing to Jira.
  • Fixed an issue in Jira where users with certain scripted fields were unable to create a collection.

Microsoft TFS

  • Improved the Microsoft Team Foundation Server connector to better handle irregular person field values on work items.
  • Fixes an issue where unexpected user values returned from the TFS server were blocking Tasktop from running.
  • Fixed an issue where modifying a Microsoft TFS collection name could lead to HTTP errors.

VersionOne

  • Fixed an issue where an invalid web link value (e.g. one with spaces in the URI) could cause artifact retrieval to fail. These values are now being ignored.

 

Upgrade Notes

CA Agile Central (Rally)

  • Users authenticating with API Key in the username field will be automatically migrated to use the “API Key Access” authentication option, and have their username cleared out.

 



Jama Integration Hub (JIH) UPGRADE VERSION 4.13.3

Published: 2018/01/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 major feature updates across all connectors, including the ability to authenticate with Jama using OAuth.

 

Features since 4.12.11

Atlassian Jira

  • Epic Link field in Jira Connector is now the Parent smart field.

CA Agile Central (Rally)

  • CA Agile Central (Rally) connector is now able to retrieve more than 2000 options for single-select fields on supported versions.
  • CA Agile Central now supports query language searches on more fields

Jama

  • Jama connector can now authenticate using OAuth 2.0.
  • State transitions are now supported in Jama.
  • Users can now route by Jama Components.

Microsoft Team Foundation Server

  • Added the ability to treat custom TFS person fields as PersonHandle fields instead of ValueWithLabel fields in TFS 2017+ repositories.

VersionOne

  • IsClosed is now writeable on VersionOne artifacts, allowing to manipulate the asset state of artifacts to being closed and open.
  • The application now supports VersionOne’s new Tags field.

 

Fixes since JIH 4.12.11

General Fixes

  • During proxy association export, refresh option now removes local tasks that have been deleted in the repository.
  • 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.
  • Fixed issue that allowed a task to match multiple mappings with different, overlapping queries.

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.
  • Optimized change detection of Jira artifacts.
  • Fixed Epic Link appearing as read-only when Epic issue type is renamed.
  • Fixed an issue causing degraded performance while synchronizing the Test Case artifact on Jira Cloud.
  • Fixed an issue with mapping a JIRA nFeed field in a collection.

HPE ALM

  • Fixed 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.
  • Dev now accepts all characters in password and username field for HP QC.

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 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).
  • Fixed an issue where repository credentials would validate, but artifact retrieval failed due to invalid credentials for REST calls.
  • Fixed an issue where creating an artifact would cause an error in TFS 2015 RTM.
  • Fixed the Microsoft Team Foundation Server connector to specify a requirement on the Team Foundation Server Command Line Client.
  • Fixed an issue where Tasktop Integration Hub would fail to transition a Microsoft Team Foundation Server work item to a new state.

VersionOne

  • Fixed an issue where retrieving an artifact that had been closed by a deleted user would cause an error.
  • Fixed an issue with the VersionOne connector where it was unable to support the VersionOne On-Demand Fall 2017 Update.

 

Upgrade Notes

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

 

Connector-Specific Upgrade Notes

  • 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.

 



Jama Integration Hub (JIH) UPGRADE VERSION 4.12.11

Published: 2017/12/19 

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
      1565 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. :)