Skip to main content
System StatusContact Support
VersionOne Community

V6.16-U1

This update brings support for Team Foundation Server (TFS) 2018, as well as, other enhancements and fixes.

New Connectors and Versions

  • Team Foundation Server 2018 

New DB Support

  • MySQL V5.7.20

Fixed

  • Integration won’t be blocked for all configured projects if any project(s) are deleted/archived/inaccessible. Sync will continue smoothly for rest of the projects and job error will be logged for missing projects. If a customer has configured failure notification, then integration failure updates will contain details of missing projects.
  • Performance improvement while logging in ALM Connect and activating integrations when a high number of integrations are enabled 

Known Behavior

  • ALM Connect

    • Failure counts varies between integration page and report page if sync fails after workflow execution

  • JAMA  

    • Updates on field with status transition enabled getting missed when that field is updated with some other field in same revision  

  • VersionOne

    • Few fields not visible during mapping configuration if VersionOne is the target system

  • JIRA Service Desk

    • When fetching comments information from Jira Service Desk, comments were not getting polled because Jira Service Desk gave information for whether the comments are private or public as a string or Boolean 

  • Microsoft Team Foundation Server/ Visual Team Foundation Server

    • Integration recovery not working properly when Impersonation and Bypass are enabled     

    • Test results synchronization was failing with event failures

    • Parameters of test cases was not synchronizing 

  • ServiceNow

    • If “Include author detail in Comment” is enabled in Comments mapping, spacing between author name and actual comment body was coming in new line

Known Issues

  • Sync fails if iteration name in VersionOne contains “/”
  • Was this article helpful?