Tasktop Integration Hub (TIH) Release Notes

By Kristina posted 02-09-2017 16:26

  

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.
0 comments
755 views