Skip to main content
System StatusContact Support Agility Community

Continuum Release Notes 20.0

20.0 Highlights


VS Exchange

image (12).png

As new users begin working with Continuum many times users will start to take advantage of Continuum capabilities to extend VersionOne or another product. For example, if a story goes into developing without having any tests.  In this case Continuum has been extended to catch this story and move it back to ready for development with a blocker that tests need to be added. With the introduction of VS Exchange users will soon be able to submit pull request to our VS Exchange repo for review.  These new extensions are community driven, accepted extensions will be visible in the Continuum UI. Currently we are using Solution Architects and Services team members in conjunction with customers to pilot this new feature. 

Team Level Plugin Support

image (15).png

As an enterprise there may be times when plugins need to be restricted.  For example, an enterprise may need each team to use a specific Jenkins token.  With team level plugins when an instance of that plugin, Jenkins in this case, is created a team can be assigned. This will allow that team to only use that instance or available global plugin instances. 

Plugins that Support Teams:

  • VersionOne
  • Jenkins
  • Bitbucket
  • Jira
  • TeamCity
  • GitHub
  • GitLab
  • Azure DevOps


  • The status filter on the pipeline instance page was behind the column headers.
  • Viewing build plugin detail can cause the system to freeze.
  • Manual activity email does not replace template variables.
  • When multiple controls are present within an activity, clicking on any control always presents the data for the first.