Tasktop Integration Hub (TIH) Release Notes

By Kristina posted 02-09-2017 16:26

  

Tasktop Integration Hub (TIH) UPGRADE VERSION 19.2.4

Published: 05/17/2019 (Download Tasktop 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
      • Tasktop Integration Hub Fixes
        • Activity & Issues
        • Infrastructure
        • Installers
      • Connector-Specific Fixes
        • Planview LeanKit
        • ServiceNow
    • Features
      • Connector-Specific Features
        • BMC Remedy

    Fixes

    Tasktop Integration Hub Fixes

    Activity & Issues

        • 94069: Fixed an issue where troubleshooting logs incorrectly stated that changes were not applied for mapped fields when fields had synchronized successfully.

        • 92899: Fixed an issue where the maximum error limit was reached due to retrying 'ignored' errors.

    Infrastructure

        • 95350: Tomcat has been upgraded from version 8.5.34 to 8.5.40. This should resolve issues users may have experienced in Chrome.

    Installers

      • 95912: Fixed an issue where OEM installations were unable to start.

    Connector-Specific Fixes

    Planview LeanKit

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

    ServiceNow

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

    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.


Tasktop Integration Hub (TIH) UPGRADE VERSION 19.2.3

Published: 05/08/2019 (Download Tasktop 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
    • Tasktop Integration Hub Upgrade Notes
      • Artifact Relationship Management (ARM)
      • Container Synchronization
      • Operational Database
      • User Management
    • Connector-Specific Upgrade Notes
      • General (Services)
      • Atlassian Jira
      • BMC Remedy
      • Micro Focus ALM
      • Micro Focus ALM Octane
      • QASymphony qTest Manager
  • Fixes
    • Tasktop Integration Hub Fixes
      • Activity & Issues
      • Artifact Relationship Management (ARM)
      • Collections
      • Container Synchronization
      • Enterprise Data Stream
      • Extensions
      • Gateway
      • Integrations
      • Operational Database
      • Product Upgrades
      • Repositories
      • Settings
      • State Transitions
      • Twinless Artifact Update
      • User Management
    • Connector-Specific Fixes
      • Atlassian Jira
      • BMC Remedy
      • CA Agile Central (Rally)
      • GitHub Issues
      • GitLab 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
      • Planview Enterprise
      • Planview LeanKit
      • PTC Integrity Lifecycle Manager
      • QASymphony qTest Manager
      • Salesforce
      • Targetprocess
      • Trello
      • Tricentis Tosca
      • WhiteHat Sentinel
  • Features
    • Tasktop Integration Hub Features
      • Collections
      • Help
      • Integrations
      • Operational Database
      • Product Upgrades
      • Settings
      • User Management
    • Connector-Specific Features
      • Atlassian Jira
      • Blueprint
      • BMC Remedy
      • CA PPM
      • GitLab Issues
      • IBM Rational Team Concert
      • 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
      • Mozilla Bugzilla
      • Pivotal Tracker
      • Planview Enterprise
      • QASymphony qTest Manager
      • ServiceNow
      • SmartBear QAComplete
      • Sparx Systems Pro Cloud Server
      • Targetprocess
      • Tricentis Tosca
      • VersionOne
      • XebiaLabs XL Release
      • Zendesk

Upgrade Notes

Tasktop Integration Hub Upgrade Notes

Artifact Relationship Management (ARM)

    • 93769: The transforms listed below are no longer available in editions that do not include the Git connector. These transforms were designed for use in SCM integrations specifically, and have high performance impacts on other integration types. 
      • String to Relationship(s) by ID 
      • Rich Text to Relationship(s) by ID

Container Synchronization

    • 94970: Container Matching Settings sash is now only available for containers which can be contained by themselves (for example, ALM folders will be supported, but ALM Test Sets will not).

    • 94669: Constant value mappings that are mapped to a single selection field that has changed into container field will need to be manually re-created.

Operational Database

    • 94263: The following Operational Database and Browser versions are no longer available under Tasktop's general support. These versions are now available under extended support only: 
      • Browser: Chrome 50.0 – 72.x; Firefox 46.0 – 60.x 
      • Database: MS SQL Server: 2008, 2012; MySQL: 5.5+; Oracle: 11

      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.

    • 92908: While Tasktop is being upgraded, if any data integrity issues are discovered in the Artifact Associations table, the problematic records will be moved to a new table and associated integrations will generate an error, exposed on the Activity screen. If this happens, contact Tasktop customer support before clearing the error.

    • 91263: While we always recommend backing up the operational database, it is imperative that a backup is made prior to upgrading to this version. Upon upgrade from a previous version of Tasktop to this version or later, a one-time change to the operational database will occur that may take an hour or longer to complete. During the upgrade process, the UI will not be available. To monitor the upgrade process, please inspect the log files.

User Management

    • 91307: Existing Tasktop admins will no longer be able to access the User Administration screen in Tasktop unless they are granted view-realm and view-clients roles via the backend User Administration Console. To do this, log into the Tasktop User Administration Console. Go to Manage>Users, and select the Tasktop admin. Go to the Role Mappings tab. Under Client Roles, select ‘realm-management.’ Assign the view-clients and view-realm roles.

Connector-Specific Upgrade Notes

General (Services)

    • 94974: 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 - 14.4, 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: IT Service Management and IT Business Management (Agile Development/SDLC, PPM) - Jakarta On Demand 
      • 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 repository connection must have the 'browse users and groups' permission granted. 
      • Any existing Zephyr Cloud collections with default person reconciliation that rely solely on Jira and the target repository having identical usernames will no longer work. A person reconciliation extension will be required in such cases. Behavior for Zephyr On Premise is unchanged. 
      • Any existing extensions for Zephyr/Jira Cloud that utilize the person-username field to search or map from Zephyr/Jira must be updated to use a different field such as person-email, as Jira has replaced the username field with a user account ID to comply with GDPR. Extensions for Zephyr On Premise will not need to be changed. 
      • If there are field mappings that map Jira Cloud person fields to a string field (including mappings for Enterprise Data Stream), 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’). We recommend changing the transform to 'Person to String (Display Name)' in these scenarios. Behavior for Zephyr On Premise is unchanged. 
      • Gateway payloads sent to Tasktop using person(s) fields may need to change to send appropriate data (for example, e-mail instead of username). If using gateway collections with Zephyr Cloud, please review payloads upon upgrade and update as needed, or consider using an extension to ensure the correct data is sent.

    • 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 repository connection must have the 'browse users and groups' permission granted.

      • Any existing Jira Cloud collections with default person reconciliation that rely solely on Jira and the target repository having identical usernames will no longer work. A person reconciliation extension will be required in such cases. Behavior for Jira On Premise is unchanged.

      • Any existing extensions for Jira Cloud that utilize the person-username field to search or map from Jira must be updated to use a different field such as person-email, as Jira has replaced the username field with a user account ID to comply with GDPR. Extensions for Jira On Premise will not need to be changed.

      • If there are field mappings that map Jira Cloud person fields to a string field (including mappings for Enterprise Data Stream), 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'). We recommend changing the transform to 'Person to String (Display Name)' in these scenarios. Behavior for Jira On Premise is unchanged.

      • Gateway payloads sent to Tasktop using person(s) fields may need to change to send appropriate data (for example, e-mail instead of username). If using gateway collections with Jira Cloud, please review payloads upon upgrade and update as needed, or consider using an extension to ensure the correct data is sent.

BMC Remedy

    • 94819: We encourage all customers to move from the Remedy SOAP API to the Remedy Rest API. Switching to the Rest API will improve connector performance and eliminate dependency on custom Web Services and Forms to utilize Tasktop. Additionally, select features and defect fixes may only be available on the Rest API in future due to third party limitations. A deprecation date for the SOAP API will be announced at a future date.

    • 92679: If using the SOAP API, 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

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

    • 91733: The Subject field on Tests must 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

    • 95252: To resolve a performance issue, Tasktop may perform a one-time full scan of all artifacts within QASymphony collection(s) upon upgrade.

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

Fixes

Tasktop Integration Hub Fixes

Activity & Issues

    • 94511: Fixed a text wrapping UI issue on Activity screen.

    • 87274: Fixed a UI issue where long artifact summaries weren't properly displayed on the Ignored Errors tab.

Artifact Relationship Management (ARM)

    • 95447: Fixed an issue preventing users from mapping single relationship collection fields to multi-relationship model fields.

    • 93499: Fixed an issue where Micro Focus ALM project renames would cause persistent errors for integrations flowing relationship(s) fields.

    • 93068: Fixed an issue where artifacts were not synchronized if a related artifact was excluded from an integration by, for example, artifact filtering or routing.

    • 92362: Fixed an issue where an error was displayed when setting a relationship field value in the target repository and then setting that same relationship value in the source repository.

Collections

    • 94658: Fixed an issue where Custom Data Transformation Extensions sometimes were not available to be selected.

    • 94439: Fixed an error that occurred when mapping a field that had different IDs in each project of the collection.

    • 94329: When selecting projects for a collection and using the 'search' functionality to locate the project, users are now able to expand that project to view its children.

    • 93310: When displaying values for option mapping, empty projects are skipped and logged, rather than erroring.

    • 91929: Single- and multi-select values can now be mapped for all projects included in a collection (rather than just the first project).

    • 91108: Fixed an issue where the "String to Relationship (by ID)" value transformation would fail to find a relationship.

    • 79346: Fixed a defect where project renames were not reflected on the Collection screen (under 'Manage Projects').

Container Synchronization

    • 95062: Fixed an issue where a warning was not being shown on the field flow screen when a container synchronization did not have the hierarchy (parent) field mapped.

    • 90949: Fixed an issue where users saw an extraneous configuration warning icon for Container Mirroring when no configuration issues had occurred.

    • 85276: Fixed a UI issue for artifact creation flow arrows on the Work Item + Container Synchronization integration configuration screen.

Enterprise Data Stream

    • 92833: Fixed an issue where Enterprise Data Stream integrations failed to process removed artifacts when the Tasktop field mappings had changed since the artifact was last scanned. Note that if database field mappings are altered between the time an artifact was last scanned by Tasktop and the time it is removed from the collection, Tasktop will not be able to populate the historical values for the fields whose mappings have changed.

Extensions

    • 93734: Fixed an issue where custom data transformation extensions would fail if they included null input values.

Gateway

    • 92495: Fixed an issue where Create via Gateway integrations were not working under the following circumstances: 
      • Customer started using Hub prior to 17.2 
      • Hub upgraded to 18.4 or later 
      • Hub still using internal Derby database

Integrations

    • 95271: Fixed an issue where changes were sometimes not detected.

    • 95178: Fixed an issue where the "Relationships to URLs String" transform sometimes failed.

    • 94360: 
      • Fixed an issue where Twinless Artifact Update changes were propagated back to the source artifact upon returning to the integration. 
      • Fixed an issue where conflict resolution did not work for fields used in state transitions.

    • 91743: Fixed an issue where comments previously synchronized into TFS were duplicated upon upgrade to 18.4.

    • 91605: Conflict Resolution Strategy is now simply called Conflict Resolution.

    • 91321: Fixed an issue where previously synchronized comments or attachments were duplicated due to newly added comment/attachment metadata (e.g. synthetic comment detection).

Operational Database

    • 93543: Database communication errors that occur during upgrade migrations now cause migrations to be immediately retried.

    • 92908: Corrupt records in the Artifact Associations table will be moved to a new table when discovered. Associated integrations will be blocked.

    • 91644: Fixed an issue where Tasktop logs showed a missing table when starting up Tasktop using MySQL as the operational database.

    • 91641: Fixed an issue where certain SQL operations could time out against SQL Server during operational data migration.

Product Upgrades

    • 92514: Fixed an issue where customers with Gateway integrations and legacy database structure could experience migration issues.

    • 92408: Fixed an issue where Tasktop was unable to complete migration after upgrading for instances using Oracle 12C as their operational database.

    • 92116: Fixed an upgrade issue that impacted users upgrading from Tasktop versions 17.2 or earlier.

Repositories

    • 92053: Fixed an issue where the 'save' button was not available when Connection Security settings were modified on the Repository screen.

    • 91447: Fixed an issue where repository logos appeared broken in Internet Explorer.

    • 87356: Improved UI/instructions on the 'External Files Required' screen for Microsoft TFS repository.

Settings

    • 90622: Fixed an issue where email settings validation could block shutting down Tasktop indefinitely if the configured email server did not respond.

State Transitions

    • 92947: Fixed an issue where state transitions would not be applied if the change that triggered it also moved the artifact out of a filter.

    • 92338: Tasktop now explicitly logs state transition changes, and saves values for any field changed by a transition, not just those that were configured as part of the transition.

    • 92099: Fixed a defect where values changed by state transitions could not be accessed when doing scripted value transformations.

    • 91478: Fixed an issue where state transition extensions that set person fields may encounter an exception when performing the transition.

Twinless Artifact Update

    • 93459: Fixed an issue where Twinless Artifact Update could not create a comment when comment flow is not enabled.

    • 93140: Fixed an issue where a failed Twinless Artifact Update would duplicate comments.

    • 92339: Fixed an issue where Twinless Artifact Update could not add a comment to artifacts which already had comments.

User Management

    • 91307: Fixed an issue where admins were unable to access User Management in Tasktop after upgrading Keycloak. Please note that a realm administrator is now required to have view-realm and view-clients permissions in order to fully access User Management.

    • 90824: Fixed an issue that allowed users without the 'TasktopUser' role to access the application.

Connector-Specific Fixes

Atlassian Jira

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

    • 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 collection 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 collection 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 collections of large sizes.

    • 90964: Fixed a bug in the BMC Remedy connector where attempts to update a work item could fail when that work item 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 where the GitHub connector 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.

GitLab Issues

    • 94636: Fixed an issue where GitLab Issues with assignees were being processed as modified every time a change detection was run.

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 fields would show up as available fields for DOORS collections.

    • 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, eliminating this issue.

    • 90620: Fixed an issue where RTC changeset ordering caused false Tasktop activity entries to be logged.

    • 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 fields 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)

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

    • 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 relationships were not properly added to work items.

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

    • 91215: Fixed an issue where the Microsoft Team Foundation Server connector attempted to connect to the server over an insecure channel even if insecure connections were disallowed.

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

Planview Enterprise

    • 89657: Fixed an issue where artifacts were missed by artifact filtering due to some Planview Enterprise queries being incorrectly constructed.

Planview LeanKit

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

PTC Integrity Lifecycle Manager

    • 93720: PTC Integrity connector will now allow HTTP connections to be configured.

    • 85556: Made changes to preserve the date time formatting pattern selected by the user for PTC Integrity repositories in the event of a Tasktop Java upgrade.

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.

    • 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

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

    • 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

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

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

Trello

    • 91617: Fixed an issue where an artifact could not be retrieved if it were linked to a deleted artifact.

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.

WhiteHat Sentinel

    • 92379: Fixed an issue where some fields editable in the web UI (Summary, Custom Asset ID, Asset owner name, and Asset phase) were not triggering change detection.

    • 92240: Fixed an issue where Tasktop could not retrieve the Custom Asset ID field or the contents of the Description field for Asset (Site) artifacts.

Features

Tasktop Integration Hub Features

Collections

    • 90996: Rich text field transformations can now be configured to use a non-default markup language.

Help

    • 94045: The Support and Usage Report now contains the collection schema (the list of fields available for each collection) and collection mappings.

    • 91468: Issues shown on the Activity screen are now included in the "Support and Usage Report" zip file as activity/issues.json.

Integrations

    • 91474: When creating an integration, invalid target collections will no longer be available for selection.

    • 91275: Updated user experience on Comment and Attachment flow pages.

Operational Database

    • 94454: Implemented a caching layer to increase speed of artifact handle consolidation.

Product Upgrades

    • 92428: Created affordances for Tasktop upgrades when artifacts in existing integrations had been treated as work items historically, but are treated as containers in newer Tasktop versions.

Settings

    • 93660: Notification emails can now be configured on Cloud.

    • 93458: SMTP credentials for email notifications are no longer required if you have an open SMTP relay.

User Management

    • 91471: Added a new 403 error page for users to logout if they logged in as an unauthorized user.

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 repositories (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.

Blueprint

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

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.

    • 93816: Added support for InstanceId and Submitter fields for Incidents.  If using the SOAP API, 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.  If using the SOAP API, the version 6.2 forms (or later) must be installed on the BMC Remedy server to synchronize these fields. For details, please see Tasktop connector documentation (https://docs.tasktop.com/tasktop/connector-documentation ).

CA PPM

    • 92133: When configuring a collection, Tasktop 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.

GitLab Issues

    • 94274: Added support for GitLab version 11.9.

    • 91116: Added support for GitLab On Demand.

IBM Rational Team Concert

    • 92096: Added support for the Subscribed By field.

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

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: Added support for Micro Focus ALM 14.01 (SaaS). 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).

    • 93135: Test Set Folders are now supported as containers.

    • 93134: Test Sets are now supported as containers.

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

    • 91733: Subject field on Tests is now a container link rather than a single select field.

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

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

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

    • 90418: The predecessor field is now supported as a 'relationships' field.

Mozilla Bugzilla

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

Pivotal Tracker

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

Planview Enterprise

    • 94713: Effort and Assignees fields on the PPL level are now supported.

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.

Sparx Systems Pro Cloud Server

    • 91104: Added support for Sparx Pro Cloud Server version 3.0.

Targetprocess

    • 93906: Targetprocess connector now supports Portfolio Epics.

Tricentis Tosca

    • 94315: The Test Case smart field now maps to the Test Case field on Execution Entries. The Test Execution smart field now maps to the Execution Entry field on Execution Test Case Logs.

    • 92360: Test Case Folder and Execution List Folder are now supported as container types and can be used for container mirroring.

    • 92359: Execution Lists are now supported as containers and can be used for container mirroring.

VersionOne

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

XebiaLabs XL Release

    • 92141: Added support for XebiaLabs XL Release version 8.5.

    • 91653: Added support for template defined variables of type text, boolean, integer, date, list, list box, and set.

Zendesk

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


Tasktop Integration Hub (TIH) UPGRADE VERSION 19.1.12

Published: 04/02/2019 (Download Tasktop 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 Integration Hub Fixes

    • Artifact Relationship Management (ARM)
    • Collections
    • Gateway
    • Operational Database
    • Product Upgrades
    • State Transitions
    • Twinless Artifact Update
    • Work Item Synchronization

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
    • PTC Integrity Lifecycle Manager
    • Salesforce
    • Targetprocess

Connector-Specific Upgrade Notes

    • Atlassian Jira (REST)
    • BMC Remedy

Tasktop Integration Hub Fixes

Artifact Relationship Management (ARM)
* 92362: Fixed an issue where an error was displayed when setting a relationship field value in the target repository and then setting that same relationship value in the source repository.

Operational Database
* 93543: Database communication errors that occur during upgrade migrations now cause migrations to be immediately retried.

Collections
* 93310: When displaying values for option mapping, empty projects are skipped and logged, rather than erroring.

Twinless Artifact Update
* 93459: Fixed an issue where Twinless Artifact Update could not create a comment when comment flow is not enabled.

State Transitions
* 92338: Hub now explicitly logs state transition changes, and saves values for any field changed by a transition, not just those that were configured as part of the transition.

Product Upgrades
* 92514: Fixed an issue where customers with Gateway integrations and legacy database structure could experience migration issues.

State Transitions
* 92947: Fixed an issue where state transitions would not be applied if the change that triggered it also moved the artifact out of a filter.
* 92099: Fixed a defect where values changed by state transitions could not be accessed when doing scripted value transformations.

Work Item Synchronization
* 92691: Fixed an issue where Twinless Artifact Update would fail when an artifact changed type to leave the collection.

Gateway
* 92495: Fixed an issue where Create via Gateway integrations were not working under the following circumstances: 

  • Customer started using Hub prior to 17.2 
  • Hub upgraded to 18.4 or later 
  • Hub still using internal Derby database

State Transitions
* 92099: Fixed a defect where values changed by state transitions could not be accessed when doing scripted value transformations.

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
* 90964: Fixed a bug in the BMC Remedy connector where attempts to update a work item could fail when that work item had a field with a user that could not be validated.
* 92679: Made optimizations to the BMC Remedy connector to improve retrieving large number of persons.
* 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 collections of large sizes. 

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

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

IBM Rational Team Concert
* 92610: Fixed an issue where large attachments would fail to synchronize from IBM RTC to another repository.
* 90620: Fixed an issue where RTC changeset ordering caused false Tasktop activity entries to be logged.

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

 PTC Integrity Lifecycle Manager
* 93720: PTC Integrity connector will now allow HTTP connections to be configured.
* 85556: Made changes to preserve the date time formatting pattern selected by the user for PTC Integrity repositories in the event of a Tasktop Java upgrade.

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

 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 repository connection must have the 'browse users and groups' permission granted. 

 Any existing Zephyr Cloud collections with default person reconciliation that rely solely on Jira and the target repository having identical usernames will no longer work. A person reconciliation extension will be required in such cases. Behavior for Zephyr On Premise is unchanged. 

 Any existing extensions for Zephyr/Jira Cloud that utilize the person-username field to search or map from Zephyr/Jira must be updated to use a different field such as person-email, as Jira has replaced the username field with a user account ID to comply with GDPR. Extensions for Zephyr On Premise will not need to be changed. 

 If there are field mappings that map Jira Cloud person fields to a string field (including mappings for Enterprise Data Stream), 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’). We recommend changing the transform to 'Person to String (Display Name)' in these scenarios. Behavior for Zephyr On Premise is unchanged. 

 Gateway payloads sent to Tasktop using person(s) fields may need to change to send appropriate data (for example, e-mail instead of username). If using gateway collections with Zephyr Cloud, please review payloads upon upgrade and update as needed, or consider using an extension to ensure the correct data is sent.

 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.


Tasktop Integration Hub (TIH) UPGRADE VERSION 19.1.4

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

Tasktop Integration Hub Upgrade Notes

User Management

    • 91307: Existing realm administrators must be granted view-realm and view-clients roles via the User Administration Console in order to view the realm administration page.

Fixes

Tasktop Integration Hub Fixes

Collections

    • 91929: Options for all projects are now listed when configuring an Option Mapping.

    • 92155: User’s ability to create Relationship to Single Select mappings is restored for applicable repositories.

Container Synchronization

    • 90949: Fixed an issue where users saw an extraneous configuration warning icon for Container Mirroring when no configuration issues had occurred.

Product Upgrades

    • 92408: Fixed an issue where Tasktop was unable to complete migration after upgrading for instances using Oracle 12C as their operational database.

Settings

    • 90622: Fixed an issue where email settings validation could block shutting down Tasktop indefinitely if the configured email server did not respond.

Twinless Artifact Update

    • 92339: Fixed an issue where Twinless Artifact Update could not add a comment to artifacts which already had comments.

User Management

    • 91307: Fixed an issue where admins were unable to access User Management in Tasktop after upgrading Keycloak. Please note that a realm administrator is now required to have view-realm and view-clients permissions in order to fully access User Management.

 

Connector-Specific Fixes

  • Atlassian Jira (REST)
    • 91982: Fixed an error that occurred when trying to save a Jira collection 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.
  • GitHub Issues
    • 92481: Fixed an issue where the Github connector was unable to create Milestones against github.com.
  • IBM Rational DOORS
    • 92137: Fixed an issue where the IBM Rational Doors connector could wait indefinitely for an operation to complete.
  • 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.
  • WhiteHat Sentinel
    • 92240: Fixed an issue where Tasktop could not retrieve the Custom Asset ID field or the contents of the Description field for Asset (Site) artifacts.

Features

Connector-Specific Features

XebiaLabs XL Release

    • 91653: Added support for template defined variables of type text, boolean, integer, date, list, list box, and set.


Tasktop Integration Hub (TIH) UPGRADE VERSION 19.1.2

Published: 01/22/2019 (http://www.jamasoftware.com/download-tih/)

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

Tasktop Integration Hub Upgrade Notes

Collections

      • 90792: Earlier editions contained a defect where users would get an error when trying to edit and save the Field Mapping screen. In order to resolve this error, modify one of the relationship mappings and save. The collection should be properly editable after this.

Logging

      • 85752: Output is no longer logged to the file tasktop/logs/catalina.out on Linux because it was being duplicated in other log files. Users may want to delete the file to recover disk space.

Operational Database

      • 88800: Tasktop Integration Hub will now refuse to start if it is run on Linux as root. Running as root is not recommended; however, the user can workaround this restriction by deleting lines 3-7 from the start-tasktop.sh script. This change will need to be made with every upgrade of Tasktop. It is recommended that a dedicated user be created for Tasktop, and that user be set as the owner of Tasktop's installation directory.

User Management

    • 86643: Refer to the user FAQ (https://docs.tasktop.com/tasktop/faq ) to remediate an “open redirect” security vulnerability by configuring valid redirect URI restrictions in Tasktop’s User Administration Console.

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 repository connection must have the 'browse users and groups' permission granted.

        • Any existing Jira Cloud collections with default person reconciliation that rely solely on Jira and the target repository having identical usernames will no longer work. A person reconciliation extension will be required in such cases. Behavior for Jira On Premise is unchanged.

        • Any existing extensions for Jira Cloud that utilize the person-username field to search or map from Jira must be updated to use a different field such as person-email, as Jira has replaced the username field with a user account ID to comply with GDPR. Extensions for Jira On Premise will not need to be changed.

        • If there are field mappings that map Jira Cloud person fields to a string field (including mappings for Enterprise Data Stream), 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'). We recommend changing the transform to 'Person to String (Display Name)' in these scenarios. Behavior for Jira On Premise is unchanged.

        • Gateway payloads sent to Tasktop using person(s) fields may need to change to send appropriate data (for example, e-mail instead of username). If using gateway collections with Jira Cloud, please review payloads upon upgrade and update as needed, or consider using an extension to ensure the correct data is sent.

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 (HPE)

      • 80555: Labels for Comment Handling options on the Repository screen have been updated. Existing repositories with old selections will display as 'invalid,' but existing integrations will continue to run as expected. Users can select a value with an updated label to get rid of the 'invalid' message.

Micro Focus ALM Octane (HPE)

      • 88973: The Application Modules multi select field needs to be re-mapped in collections 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 Location (except the read-only "URL" field) are now of type String. Collections that include these fields will need to be updated - the fields will be removed and need to be added 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

Tasktop Integration Hub Fixes

Activity & Issues

      • 90749: Fixed an issue where ignoring too many errors would result in an error that "The maximum number of allowable errors has been reached."

      • 89895: Fixed an issue where certain errors were not retrying automatically upon artifact creation.

      • 89876: Removed exact Apache Tomcat version from some error pages for improved security.

      • 88658: Fixed an issue where entries for processed "SCM update integration" resulted in unclear information on the Activity screen.

      • 88032: Fixed an issue where background jobs may be labelled with an integration that they are not associated with.

      • 87339: Fixed an issue where the retry button for background jobs was not clickable in Internet Explorer.

Collections

      • 90792: Fixed an issue where some auto-mapped field mappings were improperly configured in Tasktop.

Container Synchronization

      • 90566: Fixed an issue where some valid container mirroring configurations were marked as invalid.

Help

      • 86923: Validation and failure information for email notifications is now logged when in troubleshooting mode.

Infrastructure

      • 89879: Fixed a potential clickjacking issue by blocking inclusion of Hub in an iframe.

Integrations

      • 91743: Fixed an issue where comments previously synchronized into TFS were duplicated upon upgrade to 18.4.

      • 91321: Fixed an issue where previously synchronized comments or attachments were duplicated due to newly added comment/attachment metadata (e.g. synthetic comment detection).

      • 89057: Fixed an issue where the Change Detection Screen did not display properly with low screen resolutions.

      • 88955: "Change Detection Full Scan Style" UI is only visible for supported integrations.

      • 87624: Fixed a UI issue where having many options selected on the Artifact Routing screen could prevent the user from scrolling to the bottom.

Logging

      • 85752: Output is no longer logged to the file tasktop/logs/catalina.out on Linux.

Metrics

      • 90831: Fixed a layout issue on the Metrics screen when viewed using Firefox.

Misc

      • 83859: Fixed an issue where users were not redirected properly after logging in.

Models

      • 86705: Table columns on the Model Configuration screen no longer expand unexpectedly when an invalid entry is provided for a text field.

Operational Database

      • 91641: Fixed an issue where certain SQL operations could time out against SQL Server during operational data migration.

      • 89429: Fixed slow processing when using SQL Server as the external database with a very large number of events.

      • 88800: Fixed an issue where the external database password could not be stored if Tasktop had been run as root on Linux. Transferring to an external database will now fail with a better error message if the password cannot be stored. Additionally, Tasktop will now refuse to start if it is run as root.

      • 88302: Fixed a deadlock error popup that could appear on the Activity screen.

      • 86540: Fixed a problem storing artifact data with supplementary characters when using Oracle as an external database.

Product Upgrades

      • 86054: Improved the text of the message shown when resolving a duplicate partition issue.

Repositories

      • 91447: Fixed an issue where repository logos appeared broken in Internet Explorer.

      • 88876: Repositories can now be configured to only allow secure connections.

      • 87356: Improved UI/instructions on the 'External Files Required' screen for Microsoft TFS repository.

State Transitions

      • 91478: Fixed an issue where state transition extensions that set person fields may encounter an exception when performing the transition.

      • 90017: Fixed an issue that could cause state transition extensions to execute erroneously due to certain interactions between extensions and field flow configuration.

      • 87226: Fixed a UI bug where pressing enter while adding/editing a state transition would clear the form without saving.

Tasktop Integration Hub

      • 87499: Fixed an issue where expired repository authentication could cause users to encounter errors while setting up their configuration in Hub.

User Management

      • 90824: Fixed an issue that allowed users without the 'TasktopUser' role to access the application.

      • 87752: Fixed an issue with the 'Test connection' button in the User Administration Console.

      • 86643: Fixed an issue by configuring valid redirect URI restrictions in Hub for new installations.

Work Item Synchronization

    • 88101: Changed conflict resolution behaviour to allow for unidirectional field mappings utilizing the same model field.

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 a limited amount of group options was being shown in the Jira Connector. Now all group options are visible.

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

      • 88860: Fixed a performance issue related 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.

Git

      • 89870: Insecure HTTP connections are now allowed to Git repositories.

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 collections with a very large set of artifacts could cause the Field Mapping screen to hang for extended periods of time.

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 Octane 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 relationships 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.

      • 91215: Fixed an issue where the Microsoft Team Foundation Server connector attempted to connect to the server over an insecure channel even if insecure connections were disallowed.

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

      • 89657: Fixed an issue where artifacts were missed by artifact filtering due to some Planview Enterprise queries being incorrectly constructed.

Planview LeanKit

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

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 (i.e. relationships) 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.

Trello

      • 91617: Fixed an issue where an artifact could not be retrieved if it were linked to a deleted artifact.

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.

      • 87524: Improved the performance of the Tosca connector when listing options in projects with a large number of items.

codeBeamer ALM

    • 90545: Fixed an issue where Release and Team were not listed as available fields.

Features

Tasktop Integration Hub Features

Collections

      • 88609: Unlicensed collection types are now visible and greyed-out on the 'New Collection' screen.

Help

      • 88785: Repository metadata can be found in the support and usage report download in the repository-metadata folder.

Integrations

      • 88547: User can route out of any container, but only into containers that directly support artifact creation. If the user selects more than one target on one side of a routing, then all selected options must be valid route end-points in order for there to be flow in that direction.

OEM

      • 88428: OEM customers will see different built in artifact models upon applying a license.

Settings

    • 88957: Users are now able to move routes between existing integrations to facilitate Micro Focus (HPE) ALM upgrades or to split or join integrations.

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.

GitLab Issues

      • 90390: Added support for GitLab version 11.5.

      • 89444: Added support for GitLab version 11.4.

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 'relationships' field.

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.

QASymphony qTest Manager

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

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.

      • 89247: Added support for Sub-Relational fields to the Micro Focus SBM Connector. Limited support was also added for the field Current Scheduled Item on Release Packages and Release Trains (from the Release Control plugin).

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

Sparx Systems Pro Cloud Server

      • 89352: Added support for Sparx Pro Cloud Server version 2.1.21.

Targetprocess

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

VersionOne

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


Tasktop Integration Hub (TIH) UPGRADE VERSION 18.4.8

Published: 11/28/2018 (Download Tasktop 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

User Management

  • 86643: Refer to the user documentation to configure open redirects in Tasktop's User Management application.

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 TIH 18.4.3

Tasktop Integration Hub Fixes

Tasktop Integration Hub

  • 89879: Fixed a potential clickjacking issue by blocking inclusion of Hub in an iframe.
  • 89895: Fixed an issue where certain errors were not retrying automatically upon artifact creation.
  • 83859: Fixed an issue where users are not redirected properly after logging in.

User Management

  • 86643: Fixed an issue by configuring valid redirect URI restrictions in Hub for new installations.

 

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.

Git

  • 89870: Insecure HTTP connections are now allowed to git repositories.

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.


Tasktop Integration Hub (TIH) VERSION 18.4.3

Published: 11/02/18 (http://www.jamasoftware.com/download-tih/)

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 support for new versions of connected software, enhancements and general fixes. 

Features since 18.3.11

Tasktop Integration Hub Features

Collections

    • Added transformations to append Location and Web Links to a field with Web Links.
    • Added transformations to transform Location to Web Links with the summary of the source artifact as Label of the Web Link.

Integrations

    • Unlicensed collection types are now visible and greyed-out on the 'New Collection' screen.

    • To improve performance and repository load, Tasktop no longer produces observe events for artifacts that have not previously synchronized during full scans.

    • Improved performance of the Integration Routing screen.

    • To improve performance and server load, Tasktop now optimizes each integration's full scan behavior to reduce unnecessary API calls. This behavior can be customized on each integration's Change Detection screen.

    • Added 'Code Traceability: Update Existing Work Item' integration.

    • Added 'Code Traceability: Create and Relate a Changeset' integration and 'Outbound Only Collection'.

    • Tasktop will now temporarily suspend repository interactions when an endpoint repository issues a backoff request.

Repositories

    • Tasktop will now inform the user when it has previously suspended repository interactions due to high server load.

    • Added ability to limit event rate to decrease Tasktop load on external repositories.

State Transitions

    • Fixed issues where errors occurring during state transition resulted in invalid state of synchronization

Connector-Specific Features

Atlassian Jira

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 18.3.11

Tasktop Integration Hub Fixes

Activity & Issues

    • Fixed an issue where the error message can overlap with the started, scheduled for processing, or retries text.

    • Fixed an issue where errors wouldn't automatically resolve for Jira repositories that connected via the two-way SSL authentication method.

    • Fixed an issue where Tasktop would fail to start when too many errors were present on product upgrade.

    • Fixed an issue where the retry button for background jobs was not clickable in Internet Explorer.

    • Fixed an issue where the activity screen did not load.

    • Fixed an issue where the project rename background job could cause the operational database to end up in an invalid state.

    • Improved the error message for temporary errors that pop up on the screen.

    • Fixed an issue where the retry button for background jobs was not clickable in Internet Explorer.

Artifact Filtering

    • Modifications to a model's single select field values will have the consequence of deleting associated artifact filters and conditional routing rules rather than having them become out of sync with the model.

    • Fixed an issue that prevented the artifact filter from being applied due to a missing single-select value.

Collections

    • Fixed an issue where setting a constant value for a single-select field with a large number of options could cause the browser to freeze.

    • Fixed an issue where artifacts could not be synchronized out of WhiteHat Sentinel if the site field was not mapped.

    • Fixed an issue where collections could not be created when the repository had multiple artifact types with the same label.

Container Synchronization

    • The "Process All Artifacts" button is now available for container integrations.

    • Corrected validation that allowed adding Jama work item collections under a Jama component collection in a Container + Work Item Synchronization.

Extensions

    • Fixed an issue that prevented extensions from being saved if there were two functions defined that started with the same word.

Field Flow

    • Fixed an issue where the radio buttons in the "Process All Events" dialog did not function correctly.

Installers

    • Removed extra dot in the filename for access logs in /tasktop/logs.

    • Tasktop instances without user management now require the use of encrypted connections only (HTTPS rather than HTTP) when accessing Tasktop using a web browser or any client using a Gateway collection. This behavior already applies to Tasktop instances with user management.

Integrations

    • "Change Detection Full Scan Style" UI is only visible for supported integrations

    • Fixed an issue where entries for processed "SCM update integration" resulted in unclear information on the activities UI.

    • Fixed an issue where using multiple projects in a collection could cause an error during processing for some connectors.

    • Fixed an issue where making configuration changes could cause full scans to never run.

    • “Collection is empty” issue message has been improved to more clearly identify the specific projects within the collection that are impacted.

    • Activity related to synchronization of an attachment is completed without error when the source attachment is deleted prior to synchronization occurring.

    • Fixed an issue where comments were duplicated after performing multiple project replacements on a Tasktop collection.

    • To prevent duplicate comments, the project replacement action will now also update person information.

    • Fixed an issue where an empty comment caused subsequent comments to not flow. Comments that were previously lost will not be restored.

    • Fixed an issue that could cause duplicate artifact creation when multiple linked integrations (i.e. Repository A --> Repository B --> Repository C) were run with a very short change detection interval.

    • Fixed an issue where multiple integrations processing the same artifact could overwrite changes made by one another.

    • Fixed an issue that would cause an error if a user changed the name of one of their projects if that project was being used in multiple integrations.

    • Enabled one-way attachment flow for repositories that support retrieving, but not creating, attachments.

    • Fixed an issue where Tasktop could fail to flow comments and attachments occasionally when a user recreated a deleted artifact.

    • Fixed an issue where events from a deleted repository could cause NullPointerException errors and prevent synchronization.

    • Fixed an issue where comments could be duplicated when an error occurred while storing past activity.

    • Certain configurations of repository searches could lead to excessive repository load due to retrieval of each search result as a separate call. Artifacts are now retrieved only if they have been changed or during a full repository scan. Additionally, only required fields are retrieved.

    • Added the ability to stop an integration even when the repository is no longer reachable.

Logging

    • Security improvements for the logging subsystem.

Operational Database

    • Improved performance by reducing database activity for blocked integrations.

    • MSSQL JDBC Driver version 6.4.0.jre8 exhibits a collation error during migration to an external SQLServer database. Driver version 7.0.0.jre8 does not exhibit this issue, and should be preferred.

    • Fixed an issue that could cause processing to become stuck when using MS SQL Server as an operational database.

    • Tasktop copies data successfully from Derby to Oracle when using ojdbc8.

    • Fixed an issue with updating external database settings when a TFS repository is configured.

    • Tasktop automatically reconnects to operational database if connection is lost and then restarts.

Product Upgrades

    • Fixed upgrade issue for Tasktop instances using the internal Derby database as the operational database. Note: For production instances, we strongly recommend using an external database, rather than the internal Derby database.

    • Tasktop will safely remove redundant record from database before migration to prevent database conflict key error.

    • Fixed an issue where the configuration could not be loaded due to a deleted work log (time entry) related transformation.

Redeployment

    • Fixed an issue where background processes may be labelled with an integration that they are not associated with.

Repositories

    • Fixed an issue where tooltips did not display for single select fields on the Repository screen in Tasktop.

    • Fixed an issue where the Jira two way SSL authentication method would not validate and would show an error: "property path must contain the data for the file."

    • To prevent errors after changes made to 'Script (HTTP Cookies)' repository authentication method, Keycloak windows installer now also creates authentication scripts by default.

Settings

    • Fixed an issue that prevented email notifications from being sent.

    • Fixed an issue where some errors could be erroneously excluded from email notifications, especially if a high email frequency were set.

State Transitions

    • Fixed an error that was encountered when configuring state transitions for fields required for artifact creation in the repository.

User Management

    • Fixed an issue with the Keycloak 'Test connection' button by upgrading Keycloak.

Work Item Synchronization

    • Changed conflict resolution behaviour to allow for unidirectional field mappings utilizing the same model field.

Connector Specific Fixes

Atlassian Jira

    • 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 NullPointerException error that occurred when using certain artifact filtering configurations.

    • 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 a performance issue in the Jira connector that pertains to synchronizing the Test Cycle artifact from the Zephyr Cloud plugin.
    • Fixed an issue where connector will filter out duplicate fields from a customer configuration containing the same metadata for sd-request-participants in Jira.

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

Tasktop Integration Hub Upgrade Notes

Installers

    • To improve security, Tasktop instances without user management now require the use of encrypted connections only (HTTPS rather than HTTP) when accessing Tasktop via a web browser or any client using a Gateway collection. HTTP connections are automatically redirected to use HTTPS by Tasktop. This behavior already applies to Tasktop instances with user management.

      In order to provide a secure connection, the temporary SSL/TLS certificate provided with Tasktop must be replaced. See User Guide for details: https://docs.tasktop.com/cd/user-guide/installation-primer/installation#Installation-HTTPSConfigurationHTTPS 

Integrations

    • When broadening artifact filter criteria or routing additional lower level containers (i.e. folders or sets) for a running integration, it is now recommended that users click the "Process all Artifacts" button on the Field Flow screen to ensure that all previously excluded artifacts are processed in a timely manner.

    • Existing integrations will default to new "Tasktop-Optimized" full scan style, to improve performance and server load. If desired, the full scan style can be customized on each integration's Change Detection screen.

Operational Database

    • MSSQL JDBC Driver version 6.4.0.jre8 exhibits a collation error during migration to an external SQLServer database. Driver version 7.0.0.jre8 does not exhibit this issue, and should be preferred.

Product Upgrades

    • Time entry fields are not supported in Tasktop Integration Hub. Any existing collections with time entry fields mapped will result in an error. Please remove any field mappings for time entry type fields.

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


Tasktop Integration Hub (TIH) VERSION 18.3.11

Published: 9/19/18 (http://www.jamasoftware.com/download-tih/)

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. 

Fixes since 18.3.5

General Fixes

  • Fixed an issue where comments were duplicated after performing multiple project replacements on a Tasktop collection.
  • Fixed an issue where errors wouldn't automatically resolve for Jira repositories that connected via the two-way SSL authentication method.
  • Added the ability to stop an integration even when the repository is no longer reachable.
  • Fixed an issue where the Jira two way SSL authentication method would not validate and would show an error: "property path must contain the data for the file."
  • Fixed an issue where errors wouldn't automatically resolve for Jira repositories that connected via the two-way SSL authentication method.
  • Fixed an issue where setting a constant value for a single-select field with a large number of options could cause the browser to freeze.
  • To prevent duplicate comments, the project replacement action will now also update person information.
  • Fixed an issue where the Jira two way SSL authentication method would not validate and would show an error: "property path must contain the data for the file."
  • Fixed upgrade issue for Tasktop instances using the internal Derby database as the operational database. Note: For production instances, we strongly recommend using an external database, rather than the internal Derby database.

Connector Specific Fixes

Atlassian Jira (REST)

  • Fixed NullPointerException error that occurred when using certain artifact filtering configurations.

 


Tasktop Integration Hub (TIH) VERSION 18.3.5

Published: 2018/07/09 (http://www.jamasoftware.com/download-tih/)

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 all repositories. 

Features since 18.2.19

Activity & Issues

  • Background jobs can now be filtered by status.
  • Failed background jobs related to Tasktop upgrades now have a retry button.
  • A 'Background Jobs' tab is now available on the Activity screen. Users can view progress on the following types of processes on the Background Jobs tab: Artifact Pair Import (when redeploying from Tasktop Sync), Integration Data Migration (when upgrading Tasktop versions), Project Replacement (when replacing invalid projects in Tasktop collections).
  • A progress bar is now shown on the Background Jobs tab of the Activity screen.
  • Added a tab where users can view and unignore previously ignored errors.
  • Added a button to ignore errors on the Activity screen.

Collections

  • Tasktop applies project replacements for invalid projects to all operational data stores.

Container Synchronization

  • Integration template name changed from 'Work Item Synchronization + Container Mirroring' to 'Container + Work Item Synchronization.'

Field Flow

  • Field flow screen now displays model fields in a column in the center.

Integrations

  • Added a screen for configuring change detection/full scan intervals for each collection in each integration. These settings will override the global change detection/full scan intervals if set.
  • When attachment flow is enabled on a running integration, Tasktop will now flow all attachments on relevant artifacts (instead of only new attachments after attachment flow is enabled). If retrieving artifact information from an Artifact Pair file, Tasktop will initially retrieve attachments to ensure they are not duplicated.
  • When comment flow is enabled on a running integration, Tasktop will now flow all comments on relevant artifacts (instead of only new comments after comment flow is enabled). If retrieving artifact information from an Artifact Pair file, Tasktop will initially retrieve comments to ensure they are not duplicated.
  • Users will now see the last-selected view ("Landscape" or "List") when returning to the Integrations screen.

Metrics

  • User counts are now available for each integration and repository in the corresponding tables on the Metrics screen. Note that Tasktop begins to collect this data after installing this version of Tasktop.
  • Users can now filter by model on the Metrics Dashboard. Metrics based on model are also displayed in a blue bar underneath the Artifacts Created and Artifact Updates counts.
  • The Metrics screen now provides a unique URL based on the selected filters (for Tasktop editions that include filtering capabilities).

Misc

  • Tasktop's internal bundle has been upgraded from Tomcat 7 to Tomcat 8.5.

Product Upgrades

  • Failed background jobs related to Tasktop upgrades now have a retry button.
  • User can have past activity migration complete successfully even in the face of repository-related errors.
  • If a configuration migration fails, the user is now able to retry the migration through a button on the issues tab of the Activity screen.
  • Integrations unrelated to a configuration migration error will no longer be prevented from starting.
  • Migrations show up in the Background Jobs tab of the Activity screen. Integrations may start processing as soon as migration for that integration completes.

Repositories

  • For increased security, the 'Script (HTTP Cookies)' repository authentication method now allows the user to select the cookie script from a list, rather than being uploaded via the UI. Please see user guide for additional details.

Settings

  • The default full scan interval is now 24 hours. This change will not impact users who upgrade from earlier Tasktop versions unless they click the 'Restore Defaults' button on the Settings screen.
  • Added functionality for email notifications for Tasktop errors and issues.

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.

Fixes since 18.2.19

General Fixes

  • Fixed an issue where multiple integrations processing the same artifact could overwrite changes made by one another.
  • Fixed an issue where artifacts could not be synchronized out of WhiteHat Sentinel if the site field was not mapped.
  • Tasktop will safely remove redundant record from database before migration to prevent database conflict key error.
  • Tasktop’s internal bundle has been upgraded from Tomcat 7 to Tomcat 8.5. Customers with customized Tomcat configuration may have start-up issues if using the old customized configuration. Please contact Tasktop Support for assistance if needed.
  • Existing repositories using 'Script (HTTP cookies)' authentication method will continue to work normally. However, if changes need to be made to existing repository configuration, users will need to follow the new process of placing the script in the designated directory.
  • Tasktop will safely remove redundant record from database before migration to prevent database conflict key error.
  • Fixed an issue that could cause processing to become stuck when using MS SQL Server as an operational database.

Activity & Issues

  • Configuration migrations will now be retried up to five times if they fail with temporary errors.
  • Fixed a UI issue for filters on the Activity screen.
  • Fixed an issue where Tasktop may experience errors and stop processing an integration which had artifact filtering configured and a stale cache.
  • Made improvements to the Activity screen UI.
  • Fixed an issue where Tasktop may surface database deadlock errors when scheduling events for processing.
  • Tasktop's activity filters are now contained in a separate panel which can be shown or hidden.
  • Fixed an issue where the project rename background job could cause the operational database to end up in an invalid state.

Artifact Filtering

  • Fixed an issue where some integrations resulted in an error when flowing artifacts with filters set on fields that contain no value.
  • Fixed an issue where configured artifact filters were not shown in the Tasktop UI. The issue occurred if one side of an integration was configured to not accept new artifacts, and a filter was configured for the other side to apply on creation and update.
  • Fixed an issue where artifacts which were previously not processed due to artifact filtering would not be processed after removing the filter and clicking the 'Process All Artifacts' button.
  • Modifications to a model's single select field values will have the consequence of deleting associated artifact filters and conditional routing rules rather than having them become out of sync with the model.
  • Fixed an issue that prevented the artifact filter from being applied due to a missing single-select value.
  • Modifications to a model's single select field values will have the consequence of deleting associated artifact filters and conditional routing rules rather than having them become out of sync with the model.

Artifact Relationship Management (ARM)

  • Improved an error message which would display "Artifact not found" for relationship to single-select field mappings instead of indicating that the mapped artifact was deleted.
  • Fixed an issue that could prevent synchronizing an artifact when a relationships field was mapped with multiple integrations configured.
  • Fixed an issue where Tasktop may experience errors attempting to remove and add relationships at the same time under certain circumstances.

Collections

  • Fixed an issue where users were unable to search the 'Work Item' list on the New Collection screen for certain inputs.
  • Improved performance for repository queries.
  • Empty string can be transformed to single select by ID or label value in field mapping.
  • Fixed an issue where relationship constant value based on projects was not displayed properly.
  • Fixed an issue where renamed Jira projects would be flagged as invalid.
  • Improved error message when formatted ID search is not available.
  • Fixed an issue where collections could not be created when the repository had multiple artifact types with the same label.
  • Fixed an issue where collections could not be created when the repository had multiple artifact types with the same label.

Container Synchronization

  • Fixed an issue which prevented container + work item synchronizations between collections of the same repository.
  • Corrected validation that allowed adding Jama work item collections under a Jama component collection in a Container + Work Item Synchronization.

Extensions

  • Added more descriptive error messages when extensions returned incorrect values.
  • Improved the Extension Code widget to expand with the screen for long scripts.

Field Flow

  • Improved an error message which would display "Artifact not found" for relationship to single-select field mappings instead of indicating that the mapped artifact was deleted.

Gateway

  • Fixed an issue where Modify via Gateway events failed when one or more projects in the collection failed to provide artifact schema.

Installers

  • Removed extra dot in the filename for access logs in /tasktop/logs.

Integrations

  • Fixed an issue where constant values were not contained within a square pill on the field flow screen.
  • Fixed an issue where long text would make field labels hard to read on the field flow screen.
  • Fixed a UI issue on the Conditional Artifact Routing screen where values in the 'Default Route' drop-down list were partially hidden.
  • Fixed an issue which would prevent state transitions from processing unless a repository artifact field changed.
  • Fixed issue where a row on the integrations screen extended beyond the width of the page.
  • Fixed an issue where attachments flowing from the DOORS connector were duplicated in the target system every time a DOORS item was processed.
  • Fixed an issue where the Artifact Routing screen would be slow to load when a collection had many containers.
  • Fixed an issue where the 'Process All Artifacts' button would not flow field values for newly mapped fields.
  • Fixed an issue where comments could be duplicated when an error occurred while storing past activity.
  • Corrected validation that allowed adding Jama work item collections under a Jama component collection in a Container + Work Item Synchronization.

Logging

  • Includes logging improvements.
  • Fixed an issue where some log messages in the log file were indented.

Metrics

  • Fixed an issue where the repository filter on the Metrics screen had the wrong label.
  • Fixed an issue on the Metrics Dashboard where "# Artifacts Created" and "# Artifact Updates" values were reversed in the Cumulative Artifact Processing Counts for Repositories.
  • Fixed an issue where filter options could not be selected on the Metrics screen.

Misc

  • Updated a third party library that could cause a deadlock in Tasktop instances with connection instabilities.

Operational Database

  • Fixed an issue where Tasktop may create unwanted duplicate artifacts if the connection to the operational database is lost at a very specific moment when processing artifacts.
  • Added validation to Tasktop's database settings to ensure that the SQL Server instance has a case sensitive collation before initiating a database transfer.
  • Tasktop copies data successfully from Derby to Oracle when using ojdbc8.
  • Fixed an issue with updating external database settings when a TFS repository is configured.
  • Tasktop automatically reconnects to operational database if connection is lost and then restarts.
  • Fixed an issue with updating external database settings when a TFS repository is configured.
  • Tasktop automatically reconnects to operational database if connection is lost and then restarts.

Product Upgrades

  • Fixed an issue that prevented some GitLab users from upgrading Tasktop.

Repositories

  • Improved Repository Connection screen UI to accommodate Authentication Method types with long names.
  • Fixed an issue where updating a repository to use a file based authentication scheme (eg. Cookie Script) from a non-file based authentication scheme (eg. Username and Password) would fail in Tasktop.
  • To prevent errors after changes made to 'Script (HTTP Cookies)' repository authentication method, Keycloak windows installer now also creates authentication scripts by default.
  • To prevent errors after changes made to 'Script (HTTP Cookies)' repository authentication method, Keycloak windows installer now also creates authentication scripts by default.

Settings

  • Fixed an issue where partial change detection scan completion could remove a full scan request.

State Transitions

  • Fixed an issue that would cause status fields using state transitions to flow backwards (from the target artifact to the source artifact) during artifact creation.
  • Improved text on State Transition screen when no state transitions are configured for a collection.
  • Updated message displayed when no state transitions are configured for a collection.

Work Item Synchronization

  • Confirmation dialogs in Tasktop no longer display values previously selected after exiting out of and reopening the dialogs.
  • Fixed an issue where events from a deleted repository could cause NullPointerException errors and prevent synchronization.

Connector Specific Fixes

Atlassian Jira (REST)

  • Fixed an issue where some Jira synchronizations were failing temporarily with an error message of 'Issue not found.'
  • Fixed an issue where attachment synchronization from Jira was failing for attachments with .htm or .html extension.
  • 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 repository connection.
  • 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 locations 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.
  • Fixed an issue where some Jira synchronizations were failing temporarily with an error message of 'Issue not found.'

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 in Jama that prevented sets from showing up on the Artifact Routing screen for text item integrations.
  • 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 with no 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

  • Time entry fields are not supported in Tasktop Integration Hub. Any existing collections with time entry fields mapped will result in an error. Please remove any field mappings for time entry type fields.
  • Atlassian Jira
  • Microsoft Team Foundation Server
  • SDK-Specific Upgrade Notes

    • Any fields utilized in an extension now must be mapped on the collection-to-model Field Mapping screen. To improve performance, fields that are not mapped to the model are no longer retrieved by Tasktop, and therefore are no longer available for use in an extension.

 


Tasktop Integration Hub (TIH) VERSION 18.2.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 fixes for Jira.

Fixes since 18.2.15
General Fixes

  • Configuration migrations will now be retried up to five times if they fail with temporary errors.
  • Fixed an issue where relationship constant value based on projects was not displayed properly.
  • Added more descriptive error messages when extensions returned incorrect values.
  • Fixed an issue where comments could be duplicated when an error occurred while storing past activity.
  • Fixed an issue which would prevent state transitions from processing unless a repository artifact field changed.
  • For increased security, the ‘Script (HTTP Cookies)’ repository authentication method now allows the user to select the cookie script from a list, rather than being uploaded via the UI.
  • Fixed an issue which prevented container + work item synchronizations between collections of the same repository.
  • Fixed an issue where Tasktop may create unwanted duplicate artifacts if the connection to the operational database is lost at a very specific moment when processing artifacts. 

 

Connector-Specific Fixes

Atlassian Jira (REST)

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

 

Tasktop Integration Hub Upgrade Notes

Existing repositories using 'Script (HTTP cookies)' authentication method will continue to work normally. However, if changes need to be made to existing repository configuration, users will need to follow the new process of placing the script in the designated directory. See User Guide for details.




Tasktop Integration Hub (TIH) VERSION 18.2.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 fixes for Jira and Jama.

 

Fixes since 18.2.11

General Fixes

  • Added validation to Tasktop's database settings to ensure that the SQL Server instance has a case sensitive collation before initiating a database transfer.
  • Fixed an issue that prevented some GitLab users from upgrading Tasktop.
  • Fixed an issue where updating a repository to use a file based authentication scheme (eg. Cookie Script) from a non-file based authentication scheme (eg. Username and Password) would fail in Tasktop.
  • Fixed an issue where Tasktop may not be able to perform change detection on an integration which has integration filters configured and a stale cache.
  • Fixed an issue where Tasktop may surface database deadlock errors when scheduling events for processing.

 

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.


Tasktop Integration Hub (TIH) VERSION 18.2.11

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

Features since 18.2.2

General Fixes

  • Improved performance for repository queries.
  • Fixed an issue where attachments flowing from the DOORS connector were duplicated in the target system every time a DOORS item was processed.
  • Fixed an issue where the Artifact Routing screen would be slow to load when a collection had many containers.
  • Fixed an issue where some integrations resulted in an error when flowing artifacts with filters set on fields that contain no value.
  • An empty string can be transformed to single select by ID or label value in field mapping.
  • Fixed an issue where filter options could not be selected on the metrics page.
  • Fixed an issue where Tasktop may experience errors attempting to remove and add relationships at the same time under certain circumstances.
  • Fixed an issue on the Metrics Dashboard where "# Artifacts Created" and "# Artifact Updates" values were reversed in the Cumulative Artifact Processing Counts for Repositories (this feature is only available in editions with advanced Metrics functionality).

Connector Specific Features

Atlassian Jira (REST)

  • 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

  • Fixed an issue in Jama that prevented sets from showing up on the Artifact Routing screen for 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.


Tasktop Integration Hub (TIH) UPGRADE VERSION 18.2.2

Published: 2018/05/02 (http://www.jamasoftware.com/download-tih/)

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 feature updates and fixes across all connectors.

Summary: This release contains fixes and enhancements including a brand new metrics dashboard, support for ALM project domain changes, support for additional operational databases, and increased versatility in container support (hierarchical structures).

Features since 18.1.19

General Fixes

  • Tasktop now provides a workflow within the collection UI to remove or replace invalid projects included in the collection.
  • Tasktop Integration Hub now includes a metrics dashboard for viewing the number of artifact creations and updates over time.
  • The Metrics screen now provides a unique URL based on the selected filters (for Tasktop editions that include filtering capabilities).
  • Tasktop can be upgraded while long running processes are waiting to be executed.

Connector Specific Features

Atlassian Jira

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

 

Fixes since 18.1.19

General Fixes

  • Fixed an issue where Extensions could not be saved if comments included a required function signature.
  • Fixed an issue where renamed Jira projects would be flagged as invalid.
  • Fixed an issue where configured artifact filters were not shown in the Tasktop UI. The issue occurred if one side of an integration was configured to not accept new artifacts, and a filter was configured for the other side to apply on creation and update.
  • Fixed an issue where the 'Process All Artifacts' button would not flow field values for newly mapped fields.
  • Fixed an issue where posting to gateway integrations could fail when a repository's authentication state had expired.
  • Fixed an issue where posting to gateway integrations could fail when a repository's authentication state had expired.
  • Fixed an issue where users would not be able to use the "Process All Artifacts" button when using Oracle or SQL Server 2008 as their operational database.
  • Fixed a problem importing artifact associations when multiple repositories have the same location.
  • Read-only connectors can now be used in container mirroring.
  • Fixed an issue where projects in the routing picker were incorrectly disabled for selection.
  • Fixed an issue where the browser would crash when trying to connect to a repository with no basic authentication.
  • Fixed a spelling mistake in a state transition error message.
  • Improved error message when a required column is missing for an SQL Collection.
  • Fixed a problem where some log messages in the log file are indented.
  • Fixed an issue where the cause of an error could not be determined due to a secondary error encountered while processing the initial error.
  • Fixed an issue where errors could occur after successfully creating an artifact in a Create via Gateway integration.
  • Fixed an issue where the username and password for a repository connection persisted, even after switching to alternate authentication methods.
  • Includes support bundle improvements.
  • Apache Commons logging configured with system properties will be overridden by the Log4j configuration.
  • Fixed an issue where a deleted project would prevent Tasktop upgrade from completing.
  • Fixed an issue where state transition graph displayed reversed source/target.
  • Fixed an issue where importing artifact associations could lead to comment duplication or issues while upgrading Tasktop.
  • Fixed an issue that would produce errors on the activity screen if Tasktop attempted to synchronize an artifact with a blank comment.
  • When attempting to update an artifact immediately after creation, Tasktop will automatically retry the event if an error occurs. This will reduce the number of errors that must be manually retried.
  • Fixed an issue where state transition graphs would not work when transitioning to indirect states (e.g. A -> B -> C with no path from A -> C).
  • Fixed an issue where clicking 'Remove All' on a filtered set of issues caused all issues to be removed instead of the filtered set.
  • Fixed a UI issue where fields in extension-based state transition configurations were improperly spaced.
  • Error message improved for scenarios where target container is missing.
  • Fixed an issue where a warning icon would appear next to valid state transition extension configurations on state transitions list.
  • Fixed UI Issue to align model label and model icon in the integration configuration canvas.
  • 'State Transition Fields' won't flicker to 'invalid' while loading a state transition configuration.
  • Fixed an issue where Gateway integration field flow would fail to load.
  • User is now shown a warning when configuring a value for the concurrency limit of a repository connection.
  • Fixed a UI issue where one-to-many and many-to-many field mappings displayed incorrectly on the Field Mapping screen.
  • Improved UI so that long names of work item types no longer cause display issues on Collections screen.
  • Fixed an issue where the proxy settings form was showing an empty password field when the user had a password saved.
  • Fixed an issue where work items were not maintained in the correct hierarchy.
  • To minimize risk of performance impacts, Tasktop now shuts down processing services in parallel instead of sequentially.
  • Gateway collection model names on the Collections screen now truncate when too long.
  • Fixed an issue where tomcat-users.xml file was missing from the distribution.
  • Fixed an issue where Windows would prematurely terminate the Tasktop process during an OS shutdown.
  • Fixed an issue where integration was incorrectly identified as a container + work item integration.
  • User is now informed if a change to a field mapping invalidates a state transition configuration.
  • When a project is removed from a collection, if the remaining projects do not contain the selected artifact type in their schema, Tasktop will remove the selected artifact type from the collection. In prior versions, the display would (incorrectly) indicate that the artifact type had not been removed. This UI issue has now been resolved.
  • Fixed an issue where deleting an integration did not actually delete it.
  • Made improvements to state transition configuration workflow and UX.
  • Fixed an issue where user was asked to re-enter the master password after migrating to an external database.
  • Fixed an issue that prevents the user from selecting fields for a state transition extension.
  • Fixed an issue where errors during state transitions would prevent other artifact changes from being logged.
  • Fixed a UI issue where the repository card on the right side of a Work Item Synchronization + Container Mirroring integration was invisible on the integration configuration screen in Internet Explorer.
  • Fixed an issue where restoring a deleted artifact after it was recreated by Tasktop caused the target artifact to receive updates from both the deleted/restored artifact, and the recreated artifact.
  • Added dialog to warn users that clicking the 'x' to remove both collections from an imported work item synchronization would actually delete the integration.
  • When merging existing integrations into a Work Item Synchronization + Container Mirroring integration, user can now see a tooltip displaying full integration name for integrations with long names.
  • To improve problem diagnosis, Tasktop will now perform periodic thread dumps to the logs in the case of a blocked shutdown.
  • Fixed an issue which prevents searching options by using special character "\".
  • Errored out comments and attachments events will get retried on temporary failures.
  • Fixed an issue that prevented change detection from completing for collections that have no artifacts.
  • Fixed an issue where an error was encountered during change detection.
  • Improved UI on collections screen to truncate long model names.
  • Fixed an issue where an artifact that should have been filtered out was causing an error.
  • Fixed an issue that prevented the database override screen from appearing.
  • Fixed an issue preventing repository queries containing string field(s) from being saved.
  • Affected field value mappings are now automatically updated when a model value is renamed.
  • Fixed text layout on Gateway collection card.
  • Fixed an issue that prevented the external database settings section from displaying, after entering the master password.
  • Fixed a UI issue where text overlapped when specifying a key on the Field Flow screen for a Modify via Gateway integration.
  • Fixed inconsistent units used in metrics calculations for metrics.json file in the support and usage reports.
  • Adjusted UI of Artifact Filtering screen.
  • Fixed an issue which prevented long field values from displaying on the Field Configuration screen.
  • Removed non-applicable 'none' extension option from state transition menu.
  • Fixed an issue where log files incorrectly contained SEVERE log entries about potential memory leak.
  • Fixed an issue where posting to gateway integrations could fail when a repository's authentication state had expired.
  • Fixed an issue which could cause passwords to be included in logs.
  • Includes logging improvements.

Connector-Specific Fixes

Atlassian Jira (REST)

  • 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.
  • 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.
  • 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.
  • Fixed an issue that prevented synchronization with certain versions of Jama.

Microsoft TFS

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

 

Upgrade Notes

Tasktop Integration Hub Upgrade Notes

  • When upgrading to 18.2.0 or later, you will see the 'Save' button enabled automatically on the Container Mirroring screen for any existing 'Work Item Synchronization + Containment Mirroring' integration. This is because of the new Container Matching Settings sash. The integration will continue running without a matching strategy in place (as it did in earlier versions), but an updated matching strategy can be selected and saved (to apply to new container artifacts that are synchronized).

 

Connector-Specific Upgrade Notes

CA Agile Central (Rally)

  • Users authenticating with an API Key now use the "API Key Access" authentication option.

Microsoft TFS

  • If a user saved a Personal Access Token in a previous version of Tasktop Integration Hub, the value of that token will be retained during an upgrade. Personal Access Token authentication will be selected.



Tasktop Integration Hub (TIH) UPGRADE VERSION 18.1.13

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 feature updates and fixes across all connectors.

Features since 18.1.13

General Fixes

  • Tasktop will now more efficiently search even when connectors do not support all search operations.

Fixes since 18.1.13

General Fixes

  • Fixed an issue where posting to gateway integrations could fail when a repository's authentication state had expired.
  • Fixed an issue where users would not be able to use the “Process All Artifacts” button when using Oracle or SQL Server 2008 as their operational database.
  • Fixed an issue where the browser would crash when trying to connect to a repository with no basic authentication.
  • Fixed an issue where a deleted project would prevent migration from completing.
  • Fixed an issue where association data was not migrated.
  • Fixed an issue whereby certain information not designated for inclusion in Support and Usage Reports was included in user-generated Support and Usage Reports.
  • Modified the Support and Usage Report creation process to eliminate certain information from user-generated reports.
  • Fixed an issue where errors could occur after successfully creating an artifact in a create via gateway integration.

Connector-Specific Fixes

Atlassian Jira

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

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


Tasktop Integration Hub (TIH) UPGRADE VERSION 18.1.13

Published: 2018/03/13

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 feature updates and fixes across all connectors.

Features since 18.1.3

General Fixes

  • Tasktop now rejects certain insecure passwords when configuring a connection to an external operational database.
  • Further enhancements were made to the state transition graph to prevent user errors during configuration and to alert users of fields that are no longer valid.
  • ‘tasktop’ is no longer a valid repository password.
  • Includes support bundle improvements.
  • State Transition icon added to Field Mapping screen (both collection/model pills and field mapping drop down), and Integration Field Flow screen.
  • Cross-site request forgery prevention now checks the X-Forwarded-Host HTTP header, which improves CSRFprevention when Hub is used behind a proxy.
  • Users can download a customer usage report showing which users were referenced by artifacts processed by Tasktop.

Connector Specific

CA Agile Central (Rally)

  • CA Agile Central connector now supports API Key authentication.

Fixes since 18.1.3

General Fixes

  • Fixed an issue where importing artifact associations could lead to comment duplication or issues while upgrading Tasktop.
  • Fixed an issue where the cause of an error could not be determined due to a secondary error encountered while processing the initial error.
  • Fixed an issue where the username and password for a repository connection persisted, even after switching to alternate authentication methods.
  • Fixed an issue where log files incorrectly contained SEVERE log entries about potential memory leak.
  • Fixed an issue that would produce errors on the activity screen if Tasktop attempted to synchronize an artifact with a blank comment.
  • When attempting to update an artifact immediately after creation, Tasktop will automatically retry the event if an error occurs. This will reduce the number of errors that must be manually retried.
  • Includes support bundle improvements.
  • Fixed an issue where state transition graph displayed reversed source/target.
  • Hub now shuts down processing services in parallel instead of sequentially.
  • Error message improved for scenarios where target container is missing.
  • Fixed an issue where a warning icon would appear next to valid state transition extension configurations on state transitions list.
  • Fixed a UI issue where one-to-many and many-to-many field mappings displayed incorrectly on the Field Mapping screen.
  • User is shown a warning when configuring a value for the concurrency limit of a repository connection.
  • To improve problem diagnosis, Tasktop will now perform periodic thread dumps to the logs in the case of a blocked shutdown.
  • Fixed a UI issue where text overlapped when specifying a key on the Field Flow screen for a Modify via Gateway integration.
  • Fixed an issue where the proxy settings form was showing an empty password field when the user had a password saved.
  • Fixed an issue where work items were not maintained in the correct hierarchy.
  • Fixed an issue where Windows would prematurely terminate the Tasktop process during an OS shutdown.
  • User is now informed if a change to a field mapping invalidates a state transition configuration.
  • Fixed a UI issue on the Field Mapping configuration screen where the field mapping dropdown did not display properly.
  • Fixed an issue where integration was incorrectly identified as a container + work item integration.
  • Fixed an issue where deleting an integration did not actually delete it.
  • Fixed a UI issue where the repository card on the right side of a Work Item Synchronization + Container Mirroring integration was invisible on the integration configuration screen in Internet Explorer.
  • Errored out comments and attachments event will get retried on temporary failures.
  • Fix text layout in Gateway collection card
  • Fixed an issue where Tasktop Integration Hub would not re-connect to the operational database after an operating system restart.
  • Fixed dialog box message when deleting state transition. A model saved with collection is required to configure a state transition.
  • Added dialog to warn users removing a row is actually deleting an integration
  • Integration routes are more tolerant of containers’ summary changes.
  • Fix an IE styling issue where the activity integration filtering dropdown was stretching beyond the page’s width.
  • Removed non-applicable none script option from state transition menu

Connector-Specific Fixes

Atlassian Jira

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

Microsoft TFS

  • 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 collection name could lead to HTTP errors.

Jama

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

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

  • Tasktop Integration Hub will now automatically connect to the operational database even if it is in use by another instance of Tasktop, allowing Tasktop to start automatically without user intervention in the case of improper shutdown. In the case that there is another Tasktop instance actively using the database it will lose database access and stop processing events.

Connector-Specific 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.


Tasktop Integration Hub (TIH) UPGRADE VERSION 18.1.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 17.4.11

General Fixes

  • User can now create Container type collections in Hub.
  • Graph based state transitions can now be created.
  • User can create an integration to synchronize container artifacts.
  • User can create a container + work item integration.
  • Artifact filtering user interface is enhanced with clear icon and text
  • Tasktop now records what instance is using the configuration database and does not permit multiple instances to use the configuration database at one time.
  • Added a default out-of-the-box container model.
  • Added link to Data Transformations Matrix screen to the Help screen.
  • Tasktop no longer displays the estimated count of connected users.
  • Updated the external database settings form header to reflect whether Hub is currently using an external database.
  • Upgrading will encrypt the existing external database password.
  • External database password is now encrypted.
  • If Tasktop is shutdown improperly, the user can click a button to allow Tasktop to obtain access to (to “override”) the database.
  • User can map two-way transformation from Container Link to Single/Multi-select field via Field Value Mapping.
  • State transitions configured via the UI now have the concept of “parameters”. These are the fields and values needed to perform a workflow transition.
  • Added a feature to enable creating state transitions using a graphical UI.
  • Changed behavior of resolving associated handles in target repository.
  • User can create a container + work item integration
  • User can create an integration to synchronize container artifacts.
  • Hub will utilize Query Language to to build filtering queries when the target repository supports the type of query.
  • Tasktop no longer displays the estimated count of connected users.

 

Connector Specific

Atlassian Jira

  • Parent Smart Field is now mapped to the Epic Link field in Jira for Jira Stories.

CA Agile Central (Rally)

  • CA Agile Central connector is now able to retrieve more than 2000 options for single-select fields on supported versions.
  • CA Agile Central connector now supports nested sub query expressions
  • CA Agile Central connector now supports query expressions.
  • 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.
  • Jama Component artifacts now expose internal ARM links.
  • Users can now route by Jama Components.

Microsoft TFS

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

VersionOne

  • IsClosed field is now writeable on VersionOne artifacts, allowing Tasktop to modify the asset state of artifacts to be closed or open.
  • VersionOne tags are now supported.

 

Fixes since 17.4.11

General Fixes

  • Fixed an issue which cause nodes on the integration diagram to be too close.
  • Fix UI issue with collection model names.
  • Fix error in logging.
  • Fixed issue where state transition mapping was not showing up on the collection page.
  • Fixed an issue where Component conflicts could not be resolved.
  • Resolved issue where state transition extensions failed after upgrading to 17.4 by ensuring that the fields migrated to the new state transition extension configuration came from the model, rather than the collection.
  • Fixed an issue where navigation menu at top of screen was not displayed when database settings were invalid.
  • Fixed an issue where the Microsoft TFS SDK file would be placed in an unexpected location if the expected location did not already exist.
  • Fixed an issue where state transition extensions were not triggered when the configured model field changed.
  • Fixed an issue where state transition extensions could not be configured.
  • Fixed an issue where Tasktop was not releasing credentials handles on Windows.
  • Fixed a typo on the Collections screen.
  • Fixed an issue where users were not able to map values from different projects.
  • Fixed an issue where changing a field caused the value in a dependent select field to become invalid.
  • Fixed an upgrade issue by better handling fields with fieldTemplate that has no standardField.
  • Fixed an issue where an error message box was appearing for an empty option mapping form when reloading the field mappings page.
  • All metrics logs snapshots are now included in the error report zip.
  • Fixed an issue where routing options were incorrectly enabled.
  • Fixed an issue where container link transform options were not being filtered properly.
  • Fixed an issue where the Field Mapping Page was not correctly filtering out the Inverse Transformation.
  • A problem was fixed which caused sporadic errors to occur in a synchronization with Micro Focus (HPE) ALM.
  • Fixed a defect where an unresolved container link relationship could cause the relationship to be removed.
  • Fixed an issue where errors involving attachments would continue to error after the issue was fixed.
  • Fixed an issue where scripted non-relationship fields were not propagated.
  • Fixed an issue where the user could not configure an option mapping with a custom data transformation extension.
  • Added a refresh button and refresh functionality to repository query page.
  • Added tooltip to option in picker
  • Fix issue where change detection encountered an unexpected error
  • Fix issue where query language search does not work
  • Fix UI issue with collection model names
  • Fixed an issue preventing repository queries that contained string field from being saved.
  • Fixed an issue that prevents the user from selecting fields for a scripted state transition
  • Removed confusing none script option

 

Connector-Specific Fixes

Atlassian Jira

  • Fixed an issue where parsing Jira nFeed user fields that did not have key field in response payload resulted 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.

Microsoft TFS

  • 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 Microsoft Team Foundation Server caused the connector to be unable 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

  • After upgrading to Tasktop Integration Hub version 17.4.10 or later, set conflict resolution strategy to have one of the collections be dominant in any Jama integration. This will resolve conflict errors for the Components field in Jama.
  • Tasktop now records which instance is using the configuration database by adding a lease record. If a Tasktop instance is terminated in a disorderly fashion (e.g. by a power outage) the database will need to have the lease record removed in order for Tasktop to reconnect to the database.

 

Connector-Specific Upgrade Notes

Microsoft TFS

  • TFS Repositories will no longer accept usernames of the form “\”. If the repository was originally setup with credentials in this form, they will need to be edited.
    To supply a domain, use the Domain field.
  • If the user has an existing Team Foundation Server repository connection, they will be prompted to upload the Team Foundation Server Command-Line Client.
  • Hub Collections that map custom person fields with TFS 2017+ repositories will need to be updated.



Tasktop Integration Hub (TIH) UPGRADE VERSION 17.4.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 general fixes and updates for Jira, TFS, HP, and VersionOne.

 

Fixes since 17.4.3

General Fixes

  • Fixed the issue where state transition mapping is not shown on the collection page.
  • Fixed an issue that caused an error to be logged after executing transitions which did not update the Status field.
  • Fixed an issue where Tasktop would not release the database lease if it was shutdown without having initialized security.
  • Fix issue where containment conflicts could not be resolved
  • Fixed an issue where transition scripts would not be able to execute if a transition had a populated artifact link field.
  • Ensure that the fields migrated to the new state transition come from the model, rather than the collection.
  • Fixed an issue where suggested mapping did not filter mapping field of type ArtifactLink to field or list of type ValueWithLabel on both mapping directions.
  • Fixed an issue that prevents Tasktop from stopping during a database transfer.
  • Fixed an issue where new artifact state may not be imported during association import.
  • Fixed issue where state transition extensions could not be configured
  • All metrics logs snapshots are now included in the error report zip.
  • Fix issue where state transition scripts are not triggered when the configured model field changes
  • Hub users are now informed of repercussions and necessary next steps after aborting a transfer to an external database.
  • Fixed an issue where Tasktop may not detect already running Keycloak instances when starting Tasktop services on Linux.
  • Fixed an issue where changing a field causes the option in a dependent select field to become invalid.
  • Fixed an issue where scripted non-relationship fields are not propagated.
  • Fixed mapping option label display when summary is undefined.

 

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.

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.

Upgrade Notes

General

  • To resolve conflict resolution on the components field, after upgrade to 17.4.10 or later version of hub, conflict resolution strategy should be set to have any of repository be dominant.


Tasktop Integration Hub (TIH) UPGRADE VERSION 17.4.3

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 fixes and major updates across the TIH interface including updates to error handling, display of data, and routing of data. Also includes are fixes and updates to CA Agile Central (Rally), JIRA, HP, Jama, and TFS. For the Jama connector specifically, the TIH now supports the ability to sync tags and route by components.

 

Features since 17.3.15

General Fixes

  • Prevents error details from being shown when the details aren’t helpful to the user
  • Models page now displays a concise view of models.
  • Added link to data transformations matrix page on the help page.
  • Improved error message when configuration change occurs during platform upgrade.
  • Repository connections can now be validated on the Repositories screen.
  • Updated the external database settings form header to reflect whether Hub is currently using an external database.
  • Blueprint, Jama and Tricentis OEM licenses can be generated with codeBeamer connector included.
  • Optimized change detection for connectors capable of supporting collection searches “sorted by recently modified.”
  • Tasktop Integration Hub supports change detection for repositories that are unable to sort search results by ‘last modified.’
  • Hub now supports mapping single-select and multi-select options when there are multiple options that have the same label.
  • User can configure and select the model fields that triggers a state transition extension for a collection.
  • User now receives an error when attempting to create an integration between HPE ALM Folder Collections, and is forbidden to route to an HPE ALM Folder if the integration is with an HPE ALM Folder Collection.
  • User can now create a collection with supported container types.
  • A pop-up is now available to show all configured constant value options for a field mapping when clicked.
  • Extensions documentation is now hosted at https://docs.tasktop.com/tasktop/user-guide/extensions.
  • Scripts are now known as Extensions.
  • User can now configure integration filters to apply when artifacts update, when artifacts are created, or both.
  • Added collapsable summary view of filters and ‘delete all artifact filters’ button.
  • Introduced project-based filtering.
  • Directional integration filters (filters that only apply to one repository in the integration) can now be configured.
  • Artifact filtering user interface is enhanced with clear icon and text.
  • Artifact routing will continue to function after a connector has added new levels of containment.
  • User can map both way transformation from Container Link to Single/Multi-select field via Option Mapping.

 

Connector Specific Features

Atlassian Jira

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

HP 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 17.3.15

General Fixes

  • Fixed an issue where synchronizing a Microsoft Team Foundation Server rich text field would cause an error.
  • Corrected problem where occasionally some activity wasn’t processed before others after prioritizing it on the Activities page.
  • Updated error messages to refer to ‘extensions’ instead of ‘scripts.’
  • The error message has been improved when the ID column of a reporting database table is not present.
  • Improved the error message produced when connection settings can’t be used to establish a connection.
  • One-way integration arrow now refers to ‘One-way Modification’ instead of ‘One-way Creation’ if integration does not support creation.
  • Fixed an issue where person reconciliation was named inconsistently.
  • Fixed an issue which could cause an error when reporting metrics.
  • Fixed a defect where comparing text that only differed on types of quotes caused a conflict.
  • A new self-signed certificate is provided for https testing purposes.
  • Improved formatting for rich text and artifact link values in past activity field changes.
  • Fixed typo in extension guide.
  • Fixed an issue where “Update Always” on single relationship field to multi-relationship field would cause an error.
  • Improved trace logging when comments are impersonated.
  • Fixed an issue which could cause slow migration when migrating activity.
  • Fixed an issue which would cause invalid field flows if the model was changed.
  • Added an error message when project configuration is outdated.
  • Fixed an issue where activity from full scans was not removed when cancelling current activity.
  • Fixed an issue which could prevent artifacts from processing if a value transformation script was used with Relationship fields.
  • Improved validation when mapping read-only fields.
  • Fixed an issue where ‘person not found’ errors had incorrect information.
  • Fixed an issue which could cause errors when configuring the master password.
  • Fixed an error where mapping single container link collection field to multi artifact link resulted in an error.
  • Fixed an error where cached artifacts were not found when attempting to map fields.
  • Updated interface for configuring repository queries in a collection to show multiple dropdown menus.
  • Fixed project-based constant mapping configuration for multi-select fields being incorrectly cleared on page load.
  • Fixed an issue where Relationships fields using Always Update would not replace existing Relationships.
  • Fixed an issue where the integration could not be saved after removing a collection.
  • Fixed an issue where multi-constant values don’t show up on the Field Flow page.
  • Updated font size for info paragraph on the Collection screen.
  • Fixed an issue where unresolved artifact link errors from a script during artifact creation were causing unretriable errors.
  • Adapted ‘suggest mappings’ button layout for smaller width screens.
  • Fixed an issue where person tracking could disrupt artifact processing.
  • Fixed an issue causing an error when using Relationships fields with Always Update.
  • The start-tasktop.sh script has been changed so that no more than 1 instance of a keycloaked version of tasktop can be started at the same time.
  • Fixed an issue which could cause errors if a Repository Query were changed in a Repository.
  • Added new transform for ContainerLink to Relationships and validation against Relationship model field to Relationships collection field mapping in the UI.
  • Fixed an issue where option mappings were incorrectly being displayed as being automatically mapped.
  • Added support for integer outputs from person reconciliation scripts.
  • Fixed an issue where Models Page did not filter out internal use fields.
  • Fixed an issue where the browser does not clear the cache with a normal reload when Tasktop Integration Hub updates.
  • Removed User Federation from the Tasktop User Management Console.
  • Pressing refresh on the collection projects dialog now causes additional types to become available after installing the Zephyr plugin into JIRA.
  • Errors encountered during change detection can now be automatically resolved
  • Fixed UI incorrectly displaying that an integration filter will not be applied.
  • Fixed a filter highlighting bug and preventing users from selecting model fields to filter if they aren’t mapped.
  • Fixed an issue which could cause an error when mapping Relationships to Relationship.
  • Added a user action point in the details of recreation error message.
  • Fixed an issue where the field mapping UI froze when single-select fields had too many values. Users can now search for the values they wish to map.
  • Fix issue where routing options are incorrectly enabled.
  • Fix issue where container link transform options are not being filtered properly.
  • Fixed an issue where Linux installation installed to paths not named “tasktop” would not be able to start.
  • Fixed an issue where unreleased connectors may be displayed in Tasktop Integration Hub.
  • Fixed an issue with Migration to better handle fields with fieldTemplate that has no standardField.
  • Fixed an issue where the Field Mapping Page was not correctly filtering out the Inverse Transformation.

 

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.

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

  • For improved maintainability and disaster recovery of your production environments, we strongly recommend storing operational data on an external database. To learn more about how to store your operational data on an external database, please see our Installation Primer here: https://docs.tasktop.com/tasktop/user-guide/installation-primer.

 

Connector Specific

Microsoft Team Foundation Server

  • After migration, Hub must be restarted if there are any collections that have option mappings for the Work Item Type field.
  • After upgrading Tasktop Integration Hub, the user will need to perform the following steps: 
    - Stop the application. 
    - 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. 
    - Start the application. 
    - 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.120.0, upload file “TFS-SDK-14.120.0.zip”.

 


Tasktop Integration Hub (TIH) UPGRADE VERSION 17.3.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 17.3.11

General Fixes

  • Fixed an issue which could cause an error when mapping Relationships to Relationship

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.


Tasktop Integration Hub (TIH) UPGRADE VERSION 17.3.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 JIRA, HP, and TFS as well as UI and error handling improvements. 

Fixes since 17.3.8

General Fixes

  • Improved error handling when comments or attachments are created.
  • Fixed an issue where the order of values in a list could cause a conflict.
  • Improved performance of the UI when there are many configuration elements.
  • Models page now displays a concise view of models.

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

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.


Tasktop Integration Hub (TIH) VERSION 17.3.8

Published: 9/15/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 general bug fixes.  

Fixes since 17.3.4

General Fixes

      • Improved performance when handling a large number of pending activity and Microsoft SQL Server is used as an external database. Improved trace logging when comments are impersonated.
      • Added an error message when project configuration is outdated.
      • Connector-Specific Fixes Atlassian JIRA Fixed an issue with retrieving options for closed issues.
      • Fixed an issue with the rank field in the creation screen.
      • HP ALM 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 HP ALM where line break characters were being removed from the text.
      • Jama Fixed an issue that caused some artifact types to be missing when using a SOAP version Microsoft Team Foundation Server ‘Wrong data type’ errors are now retried by the Microsoft TFS connector.
      • Fixed an issue where the TFS connector would sometimes stop processing items.
      • Fixed an issue where the comment header was missing when synchronizing comments to Microsoft’s Team Foundation Server.
      • Rally Fixed an issue where only the first 20 options were returned for single-selects.

Tasktop Integration Hub (TIH) VERSION 17.3.4

Published: 2017/08/22 (http://www.jamasoftware.com/download-tih/)

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 bug fixes, and fixes for JIRA, TFS, Rally and HP. 

Fixes since 17.3.1

General Fixes

      • A new self-signed certificate is provided for https testing purposes.
      • Fixed an issue where “Update Always” on single relationship field to multi-relationship field would cause an error.
      • Fixed and issue which could cause slow migration when migrating activity.
      • Fixed an issue that would prevent migration from automatically retrying in certain situations.
      • Fixed an issue where activity from full scans was not removed when cancelling current activity.
      • Improved validation when mapping read-only fields.
      • The error report now includes a thread dump.
      • Fixed an error where mapping single container link collection field to multi artifact link results in an error.
      • Fixed an issue where Relationships fields using Always Update would not replace existing Relationships.
      • Fixed an issue causing an error when using Relationships fields with Always Update.
      • Users can configure a mapping from container to relationships bidirectionally.
      • Fixed an issue that cause the database to continuously grow when the Full Scan Interval is set to a low value.
      • Log number of events that are cleaned up when migrating to a newer version.
      • Fixed an issue which could prevent artifacts from processing if a value transformation script was used with Relationship fields.
      • Fixed an issue which could cause errors when configuring the master password.
      • Fixed an issue with the String format when transforming Date or DateTime to String.
      • Updated interface for configuring repository queries in a collection to shows multiple dropdown menus.
      • When the label of a collection type changed, user is notified and can resolve the change by saving the collection with the updated type value.

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

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

Microsoft Team Foundation Server

      • Updated TFS connector documentation images.

Rally

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


Tasktop Integration Hub (TIH) VERSION 17.3.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 and feature enhancements across connectors, including the ability for read-only fields in Jama's UI to be synced using the "Allow API Override" option for that field. Bugzilla is now supported by the TIH.

Features since 17.2.6

General Fixes

Activity & Issues

      • Starting an integrations will schedule the change detection to run in 5 second (or earlier if a smaller interval is configured).
      • User can choose to recreate a deleted paired artifact of a previously synchronized artifact pair in the errors view when a change for the still existing artifact has occurred.
      • Improved navigation on the activity page when there are multiple pages

Collections: Repository

      • Collections can be created for read-only connectors.
      • User can set a constant value mapping for a multi select field.
      • Only display read only icon beside fields which are both required and read only.
      • Improved field-dropdown sorting and search-ability.

Help

      • Tasktop error report filename contains timestamp of creation.

Installers

      • The genuine Tasktop Hub linux installer displays EULA before installation.
      • On Windows, Tasktop adds Start Menu shortcuts for starting and stopping Tasktop.

Misc

      • The Master Password is encrypted and stored on a registry for Windows hub instance so that hub can automatically consumes it at startup.
      • Hub administrator can upgrade Tasktop when using Oracle as a back-end.
      • Hub administrator can migrate to Oracle from Derby.
      • Tasktop users can now upload proxy association exports via the Tasktop administrative UI.
      • Access to the Integration landscape diagram can be restricted based on the license.
      • Attachment ignored message is now logged at ‘info’ level.
      • User can remove empty collection boxes.

Models

      • Collection Relationship and Relationships fields can now be mapped to Single and Multi select fields

Platform

      • The Master Password is encrypted and stored so that it is not required on startup.

Settings and Licensing

      • When no license is provided, the user can see that connectors and integration templates are unlicensed.
      • Users will receive new features covered by their license when upgrading Tasktop.
      • Administrator can store configuration and other data in an external Oracle 11g, or 12c database. README.txt contains steps how to configure.

Template: Synchronization

      • Support change detection for repositories unable to sort search results by last modified.
      • Current activity can be filtered by running or stopped integrations.
      • User is able to resolve artifact and container links in value transformation scripts.
      • User can choose to re-synchronize artifacts to send values for new or changed field mappings.

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 17.2.6

General Fixes

      • Fixed project based constant mapping configuration for multi select fields being incorrectly cleared on page load
      • Fixed an issue where multi-constant values don’t show up on the Field Flow page
      • Fixed an issue where unresolved artifact link errors from a script during artifact creation were causing unretriable errors
      • Fixed an issue where a value transformation script would receive values in the wrong order if some of the values were empty
      • Fixed an issue which could cause Rally comments to be duplicated after upgrading Tasktop.
      • Unsaved changes dialog action buttons are consistent.
      • Fixed an issue that caused the first value to be selected as the default when mapping field options.
      • Fixed an issue where person tracking could disrupt artifact processing.
      • Fixed an issue where a field was not visible on the mapping page collection field selection if the field had a dependency on an other field.
      • Fixed an issue where processing activity would not be filtered on the activity page.
      • User sees Inbound Artifacts on integration landscape artifact type filter when collection does not have a type.
      • Project picker search value is not treated as regular expression.
      • Fixed an issue that stopped person not found exceptions from being raised if a person scripted returned an invalid user-id.
      • Errors while creating an artifact won’t be automatically retried.
      • While creating a collection, the repository connection can be changed, when projects had already been selected.
      • Fixed an issue which could create duplicate attachments when upgrading from 17.1 and synchronizing attachments for a Team Foundation Server.
      • The repository collection model is now displayed correctly when editing.
      • Fixed an issue where a user could not change transformation to none for person attributes.
      • Fixed an invalid error message from a mapped single-select option.
      • The documentation contains a section on how to script the creation of Web Links.
      • Smart-Field tooltip is aligned to display inside the UI to avoid being partially cut off.
      • Fixed an issue that could prevent using a value transformation script on fields with dependencies.
      • NotFoundException no longer appears in the Tasktop log for events that have completed successfully.
      • Fixed a defect preventing users from disabling comments if the comment field type became incompatible with comments.
      • Fixed an issue where PersonNotFoundException was being encountered on filtered artifacts.
      • Tasktop’s REST API can be accessed using basic HTTP authentication.
      • Added new transform for ContainerLink to Relationships and validation against Relationship model field to Relationships collection field mapping in the UI.
      • Fixed an issue when a user tried to configure a mapping that was a duplicate of another.
      • Fixed an issue preventing users from searching for single select constant values.
      • Error message correctly spells “occurred”.
      • Fixed an issue where changed model values would not be detected and synchronized.
      • Fixed an issue where the mapping counts were not being displayed right after saving a new collection.
      • Fixed an issue where the Field Mapping page would not show a newly added field mapping if one of the fields was recently loaded using the Field Mapping Refresh button.
      • Fixed an issue preventing a user from saving a transformation mapping with an artifact transition script into a collection.
      • Layout of Activity screen is improved for lower screen resolutions
      • The activities view filter can now display longer integration names.
      • Data persistence migration errors show up in the Activity UI as Issues.
      • Fixed an issue where comments could not synchronize due to an error from validation.
      • Migration progress is saved incrementally when upgrading Tasktop, enabling users to resume an upgrade that is interrupted.
      • Fixed an artifact change processing delay to improve synchronization integration performance.
      • Fixed an issue where migration could cause duplicates and field-related errors for Microsoft Team Foundation Server when master passwords were used.
      • Fixed an issue on the integration diagram that prevented the user from re-opening a repository panel after closing it.
      • Allows users to use update always to create two unidirectional mappings through a single model field.
      • Fixed an issue where changing a transformation cleared mapped options.
      • Fixed a defect where duplicate attachments could be created if a back synchronization failed during artifact creation.
      • Fixed an issue where synchronization failed if a person could not be found when synchronizing a single-value person field to a multi-value person field.
      • Arrowheads in the integration landscape diagram are now greyed out when not selected.
      • Fixed an issue where Models Page does not filter out internal use fields.
      • Fixed an issue causing “person not found” error when synchronizing between JIRA and HPE ALM.
      • Fixes an issue where the navigation bar buttons were not always highlighted.
      • Fixed an issue where the customer could not see the full model name in the landscape diagram.
      • Fixed an issue where adding attachment HPE ALM to JIRA caused artifact to be processed repeatedly.
      • Improved project selection message when creating a Zendesk collection
      • Migration will now retry migration automatically if a migration fails due to a retry-able error occurs this includes authentication state expired.
      • Fixed an issue where the browser does not clear the cache with a normal reload when Tasktop Integration Hub updates.
      • Fixed an issue where Copyright year would display NaN instead of a year.
      • Long running scripts will timeout.
      • Fixed an issue where the status transition scripts were not removed when removing the status mapping.
      • Fixed an issue where integration could use non-flowing parent folder mapping rather than artifact routing.
      • User can create a value transformation script for the ‘relationships’ type.
      • Fixed an issue where the ‘Configure’ link on the integration routing page did not link to the selected conditional routing pair.
      • Tasktop with user management will force the use of https when visiting the application in a browser.
      • Resolved connection issues are removed automatically.
      • Expected “Artifact cannot be processed” entries are only logged when troubleshooting is enabled.
      • Fixed an issue where the removal of an artifact was not recorded in Enterprise reporting integration when using container routing.
      • Fixed the alignment of long configuration labels in the UI.

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.

Jama

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

Microsoft Team Foundation Server

      • Fixed an issue with the TFS connector that improved TFS synchronization performance in Tasktop Integration Hub.
      • 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.
      • Fix failure retrieving a TFS artifact when it contains weblinks with angle brackets.

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:

      • A Master Password is now required and needs to be created on next startup if not set.

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.

Microsoft Team Foundation Server

      • After upgrading Tasktop Integration Hub, the user will need to perform the following steps:
        • Stop the application.
        • 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.
        • Start the application.
        • 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”.

VersionOne

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



Tasktop Integration Hub (TIH) VERSION 17.2.6

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 general fixes and minor updates to HP ALM and TFS. 

 

Features since 17.2.2:

<

General Fixes

      • User is able to resolve artifact and container links in value transformation scripts.

Connector-specific Features

HP ALM

      • Added support for the Test field Requirement Coverage.

 

Fixes since 17.2.2

General Fixes

      • Fixed an issue which could cause duplicate comments or attachments when synchronizing from Team Foundation Server after upgrading Tasktop Integration Hub.
      • NotFoundException no longer appears in the Tasktop log for events that have completed successfully.
      • Fixed an issue where PersonNotFoundException was being encountered on filtered artifacts.
      • Fixed an issue preventing a user from saving a transformation mapping with an artifact transition script into a collection.
      • Fixed an issue where integration could use non-flowing parent folder mapping rather than artifact routing.
      • No longer show errors in the UI when an event is waiting for a resource to be free.
      • Fixed an issue which would occasionally cause relationships to not synchronize.
      • Fixed an issue in RichText append transforms for Confluence markup that caused links to be duplicated.
      • Fixed an issue that caused a temporary artifact-lock error to appear in the Activity UI.
      • Fixed an issue where changed model values would not be detected and synchronized.
      • Fixed an issue that caused web links with duplicate urls to not be removed.
      • Fixed an issue where a deleted person from a repository would cause an error when synchronizing with a person mapping script.
      • Fixed an issue where comments could not synchronize due to an error from validation.

Connector-Specific Fixes

HP ALM

      • Fixed an HP ALM issue where plain text was losing formatting.
      • Fixed an issue where duplicate Test Runs were created.

Microsoft TFS

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

 

Upgrade Notes:

      • Existing Person Reconciliation Scripts need to be updated to handle null values being passed into both mapPersonFromRepository and mapPersonToRepository.



Tasktop Integration Hub (TIH) VERSION 17.2.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 add support for newer software versions, enhancements and fixes to the TIH integration UI, and fixes for all connected software.

Features since 17.1.9:

General Fixes

      • User can make HTTP requests from a script.
      • Previously existing associations for a newly created artifact are now removed.
      • User can choose to recreate a deleted paired artifact of a previously synchronized artifact pair in the errors view when a change for the still existing artifact has occurred.
      • Access to the Integration landscape diagram can be restricted based on the license.
      • User can easily create many routing groups after dropping down many items to the working space.
      • User experiences more intuitive navigation on the drill-in screen for a given field mapping.
      • User can search by metadata visible in activity UI.
      • User can filter activity by integration in the Activities page.
      • A warning icon is shown, with the cause as tooltip, when a collection to model mapping needs more configuration
      • User can map container to/from single selects fields.
      • Cache is used for listing options provided to the collection mapping ui
      • Installer on Windows is signed and published by Tasktop
      • User can choose to show models or artifact types in the integration landscape.
      • User sees landscape view as default screen and can access integrations.
      • User can create new integration from the integration landscape
      • User can filter integration landscape by model.
      • User can see more detailed view of the diagram that surfaces the underlying artifact types and the model of a given integration.
      • User can filter to show certain repositories that meets filter.
      • User can drag repos on canvas and have his layout saved.
      • User can see a visual overview of what repository connections and integrations he already has configured.
      • User can route containers for connectors that do not have project field.
      • User can map rich text fields by appending, and to/from Location fields.
      • User can set filter on model fields of type duration.
      • User can more easily add/remove projects from a routing group.
      • X.509 authentication and script-based authentication are supported.
      • User can search persons in a person reconciliation script
      • Tasktop Integration Hub supports storing configuration and other data in an external Microsoft SQL Server database.
      • Tasktop can be configured to use an external database to store configuration and other data.

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 17.1.9:

General Fixes

      • Corrected a defect where synchronization failed if a person could not be found when synchronizing a single-value person field to a multi-value person field.
      • Fixed an error when current and previous artifact links not from the same repository.
      • Fixed an issue where migration could fail for TFS when master passwords were used.
      • Fixed a defect where duplicate attachments could be created if a back synchronization failed during artifact creation.
      • Fixed an issue causing “person not found” error when synchronizing between JIRA and HPE ALM.
      • Fixed an issue where the configuration warning would not appear when an option was not mapped.
      • Fixed an issue where the customer could not see the full model name in the landscape diagram.
      • Fixed an issue where adding attachment HPE ALM to JIRA caused artifact to be processed repeatedly.
      • Fixed an issue where Copyright year would display NaN instead of a year.
      • Fixed an issue that resulted in an attachment being synchronized multiple times.
      • User can create a value transformation script for the ‘relationships’ type
      • Stack Overflow errors from scripts will report errors and events will not be lost
      • The “Require Ssl” setting in the user management configuration is now set to “None” by default.
      • Fixed an issue where model schema changes would cause errors when aggregating events.
      • Filtered artifacts no longer can cause routing related errors.
      • Added an error page when keycloak is not responding with help.
      • Configure link on integration routing page links to correct conditional routing pair
      • “Authentication state expired” issues are displayed only if they recur frequently.
      • State transition scripts can now have JIRA labels on state transition.
      • Fixed an issue where integration data can be deleted on startup during an upgrade if master passwords are used.
      • Clarify invalid mapping message for removed fields.
      • Fixed a problem connecting to Hub over SSL when using user management.
      • Migration errors are removed automatically upon a successful migration.
      • Conditional routing page displays full context of containers.
      • Fixed an issue where migrating Past Activity with a delete repository would cause a migration error
      • Successfully processed events no longer have errors in the activity view.
      • Fixed an issue where conditional route is not re-applied when condition field changes.
      • Hub cache is invalidated for model fields that accept new values if the value to be created isn’t found in the target repository
      • Integration routing page can handle many routes without crashing
      • Fixed issue where removal of artifact was not recorded in Enterprise reporting integration when using container routing.
      • Error message around migration failure improved to inform user that migration failed due to missing connector requirements
      • Fixed a problem where user management would not stop when stopping Tasktop if the system default JRE is not Java 8.
      • Not Mapped label does not appear beside fields which are mapped

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 plain text was losing formatting.
      • Fixed an issue where incorrect number of requirements could cause folder corruption.

VersionOne

      • Fixed an issue where artifacts synchronized endlessly.

Atlassian JIRA

      • Fixed a bug where results from the wrong project query could be returned
      • 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.
      • Fixed an issue so that the Atlassian JIRA connector’s person search is no longer too broad for some JIRA configurations involving LDAP.
      • Fixed error that occurred during JIRA authentication.

HP ALM

      • Fixed and issue where linked entities could not be updated.
      • Fixed an issue where expired sessions are not re-authenticated.
      • Fixed an issue where UI field text wrapping was inserting false line breaks.
      • Fixed an issue where the root elements of lookup list fields with sub-items were not available.
      • 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

      • Fixed an issue where listing deleted folders threw an ArtifactNotFoundException instead of ContainerNotFoundException.
      • 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.
      • Fixed an issue with reading error messages from Jama.
      • Fixed an issue with synchronizing lists in rich text fields in Jama.

Microsoft Team Foundation Server

      • Fixed an issue preventing schema migration in the product.
      • Fixed an issue where attachments could not be retrieved.

Rally

      • Improved error handling when retrieving an artifact associated with a deleted user.
      • Fixed an issue where network errors from CA Agile Central were not automatically retried.
      • To improve Tasktop performance, CA Central Agile collections are scoped by project and not an entire workspace.
      • Fixed an issue where some CA Agile Central single/multi select fields did not have all options available.

VersionOne

      • Fixed a problem where some requests to retrieve artifacts had URLs that were too long and caused errors.

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.
      • Users will need to refresh their schema. If they had previously mapped the Cycle field, they will need to recreate their mappings that previously mapped Cycle to a single select and change them to map to an artifact link.
      • Atlassian JIRA Sprint field has been changed and mappings using this field may need to be re-created.

HP ALM

      • Integrations mapping single and multi select fields using label may need to remap the fields. The affected fields are of Lookup list type and have at least one sub-item in available options.
      • Test Run collections currently mapping Parent Artifact field will need to remap the Parent Artifact field.
      • Mappings that use the Test Set Folder field will need updating. This field was changed from being a Single Select type to being an Artifact Link type.

Jama

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

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.

VersionOne

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

Tasktop Integration Hub (TIH) VERSION 17.1.9

Published: 4/13/17 (http://www.jamasoftware.com/download-tih/)

 Summary: This release contains fixes for HPALM, Jama, and TFS.

 Fixes since 17.1.8:

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.


Tasktop Integration Hub (TIH) VERSION 17.1.8

Available: 2017/04/04 

Summary: This release contains general fixes, and connector specific fixes for JIRA, HP ALM, Jama and Rally. 

Fixes since 17.1.7:

General Fixes

      • Fixes synchronizing duplicate attachments when an error prevents integration from processing attachment event.

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.

 

Upgrade Notes

HP ALM

      • Integrations mapping single- and multi-select fields using label may need to remap the fields. The affected fields are of Lookup list type and have at least one sub-item in available options.


Tasktop Integration Hub (TIH) VERSION 17.1.7

Available: 2017/03/22

Summary: This release contains general fixes as well as minor updates to HP ALM. 

Fixes since 17.1.6:

Tasktop Integration Hub Fixes

      • Fixed an issue where model schema changes would cause errors when aggregating events.

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.


Tasktop Integration Hub (TIH) VERSION 17.1.6


Available: 2017/03/15 

Summary: This release contains fixes to the upgrade process, and minor updates to HP ALM.

Fixes since 17.1.4:

Tasktop Integration Hub Fixes

      • Fixed an issue where integration data was deleted if configuration was not loaded.
      • “Authentication state expired” issues are only displayed if they recur frequently. Previously such issues were displayed unnecessarily.
      • State transition scripts can now have JIRA labels on state transition. Previously JIRA state transitions failed if labels were exposed on a JIRA state transition screen.

 

Connector-Specific Fixes

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.


Tasktop Integration Hub (TIH) VERSION 17.1.4

Published: 2/21/17 [Download here]

Summary: This release contains minor updates and bug fixes. 

Fixes since 17.1.0:

Tasktop Integration Hub Fixes

  • Fixed a problem connecting to Hub over SSL when using user management.
  • Fixed an issue where conditional route is not re-applied when condition field changes.
  • Fixed a problem where user management would not stop when stopping Tasktop if the system default JRE is not Java 8.

 

Connector-Specific Fixes

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.

  • Fixed error that occurred during JIRA authentication.

Jama

  • Fixed an issue with synchronizing lists in rich text fields in Jama.

Rally

  • To improve Tasktop performance, CA Central Agile collections are scoped by project and not an entire workspace.
  • Fixed an issue where some CA Agile Central single/multi-select fields did not have all options available.

 

Upgrade Notes

General

  • When upgrading to 17.1.1, the user management configuration database (User’s Tasktop data location/keycloak/standalone/data/keycloak.h2.db) must be backed up and restored after installation.

Jama

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

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.



Tasktop Integration Hub (TIH) VERSION 17.1.0

Release Date: 2017/02/08 

Summary: This is the first release of the new Tasktop Integration Hub (TIH), the next generation of the JIH. It is completely redesigned to make end-to-end integrations from requirements to tasks to tests intuitive to set up, simple to manage, and able to scale to meet enterprise-scale data management needs. 

 

Features

Activity & Issues

  • User more easily understands the impact of various Issues.

Atlassian JIRA

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

Collections

  • User can set a constant value into a ContainerLink field on a collection.
  • User can use ContainerLink like relationship field.
  • Tasktop allows Location fields to be mapped with Web Links fields.
  • Relationship field types can be mapped with Web Links field types.
  • Relationship fields can be mapped to WebLinks fields.
  • WebLink fields can now be synchronized.
  • User can set a constant value into a relationship field.
  • User can set a constant value for collection fields that accept new values but have no options.
  • User can set a different constant value on a collection field for each project in a collection.
  • User Can flow a multi-value filed to a single-value field without a script.
  • Field matching now supports matching by field label.

Collections: Gateway

  • User can populate web links fields using a gateway collection.
  • User is able to create a script that will transform an arbitrary payload into a valid gateway payload.

General

  • Artifacts known to be recently changed are processed with higher priority.

GitHub Issues

  • Added support for mapping person fields by properties such as email, display name and user name.

IBM Rational Requirements Composer

  • Support for person attributes to be mapped using person-fields (e.g. Email, User ID, User Name).

IBM Rational Team Concert

  • RTC Change Set Links now supported.

Integrations

  • User can use ContainerLinks in scripted ValueTransformations.
  • A warning is shown when making changes to running integrations.
  • Users can route artifacts to repository containers such as folders and projects.
  • User is able to configure routing with Value With Label based containers.
  • Default person is used in attachment and comment synchronization if person is not found.

Rally

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

Repositories

  • Administrators can now limit concurrency by setting a limit on the repository connection settings.
  • Added support for authentication using CA SSO.

Scripting

  • Allow value transformation scripts to handle Web Links fields.
  • Users can script custom data transformations for simple types.

Template: Synchronization

  • Artifact containers are updated when artifacts are moved between sub-containers according to new routes.
  • Synchronization of attachments can occur with repositories that reject attachment filenames with certain characters. For example, if the space character is disallowed, it is replaced with an underscore ‘_’ during synchronization to enable the corresponding attachment to flow.
  • A size limit for attachments may be specified for synchronization integrations.

User Management

  • Tasktop users must authenticate to access the Tasktop web application.

Fixes

Tasktop Integration Hub Fixes

  • User is able to list options on field mapping page for fields that depend on Container Link fields.
  • Comments can flow when a constant mapping has been configured in the same direction.
  • Fixed an issue where upgrading from 1.7.6 to 1.7.7 did not correctly migrate artifact links that did not have scope.
  • Fixed a problem where the Bulk action menu was displayed when it had no options.
  • Selecting a value for a constant mapping does not mark the page dirty before adding the mapping.
  • Labels in the conditional routing default route single select no longer overlaps with icon.
  • User can save a gateway collection after removing a repository.
  • Project pills in integration routing page always have tooltips.
  • Fixed an issue where the user could not report on deleted artifacts that were linked to other deleted artifacts.
  • Paging single select correctly enables and disables paging for a changing number of options.
  • Fixed a problem in processing a new artifact that is in multiple collections in the same integration.
  • Links will now be synchronized in both directions when a single event makes changes in both sides of a synchronization.
  • “No mapped field” message now links to the correct page.
  • User can persist state transition mapped on the collection while changing other field mapping configuration.
  • Adding a constant value after having a field selected will no longer cause an error in the saved mapping.
  • Change detection on repository collections is stopped when an expired license is present in order to prevent a large number of activity from accumulating.
  • User can navigate to comment synchronization configuration page even if type does not support comment synchronization. User is informed that the collection does not support comments.
  • Removing all projects when editing a collection no longer causes the type to disappear from the UI.
  • Comments which error will not block other comments from synchronizing.

 

Connector-Specific Fixes

Atlassian JIRA

  • Fixed an issue where retrieving an artifact with Jira Enhancer Plugin’s date field caused an error.
  • Fixed a problem when retrieving a Jira artifact with unsupported writeable fields.
  • Fixed the retrieval of attachments from Atlassian JIRA OnDemand.
  • Improved error handling when Atlassian JIRA user has insufficient permissions.
  • Fixed an issue where the JIRA connector did not retrieve single select options for a closed issue.

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.

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.

Microsoft Team Foundation Server

  • Fixed memory consumption issues with the TFS SDK.
  • Fixed an issue where date based favorite queries return no result.

Rally

  • 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.
  • 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.
  • Fixed an error sometimes seen when synchronizing newly created artifacts with parent child links.

VersionOne

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

 

Upgrade Notes

Microsoft Team Foundation Server

  • The required version of Team Foundation Server SDK for Java has changed from 12.0.2 to 14.0.2.

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.
  • 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.
1 comment
839 views

Comments

11-06-2018 10:57

Adding a comment to see if it will result in me getting notified when this page is updated.