2024.11 release - September 2024

Overview

This release contains bug fixes and minor internal improvements.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication Steps (if applicable)
Linked runbooks modal is not working for templates that have a snippet task type	Linked Runbooks	Linked runbooks is not working for any templates that have a snippet	Create a template with a snippet task type Create a new runbook Insert the template with a snippet task type The template will now be inserted successfully
SAML Mapping upload failure due to subfolder name already existing under multiple parent folders.	SAML/RBAC	SAML mapping upload failure due to subfolder name already existing	Create folders with different names Create subfolders with the same name in each of the created folders Create the SAML file according to folders and subfolders mapping Upload configured file
Include ‘Context in request’ option for Polling Webhook failed to generate a JSON object.	Integrations	As a user, when I have enabled the ‘Include Context in Request’ option I expect my JSON payload to include the _cutover_request_context but it is showing an exception error.	Create a predefined polling webhook integration connection Create an integration action under that connection that can post to an endpoint. Select 'Include context in request' Use the integration successfully in a runbook
Filtering by custom fields limited to a workspace, returns no results.	API	If you have custom fields limited to specific workspaces, and try to reference them via the API, a status 200 OK is returned but there are no results.	We've updated our API documentation to reflect how to search for workspace specific Custom Fields. If your search includes a workspace specific custom field then you must include the workspace_id parameter. You can only search for custom fields in one workspace at a time.
OAuth error not allowing users the option to debug Custom integrations.	Integrations	Users are not able to see/click on the “*debug*” option after an integration error is present within a runbook.	Create a Custom integration with OAUTH Receive an OAUTH specific error Integrations Debug would not display
API returns an error when using searchable custom fields and custom-field-values query.	API	When using the custom_field_values query within the List Runbooks endpoint, the API displays a 500 error if the custom field is a Searchable Custom Field.	Within the API Use the list runbooks endpoint Add query parameter custom_field_values The query parameter should return data as it would any other custom field

2024.10 release - August 2024

Overview

You can now start a Live run without having to add a scheduled start date first. Also, when you choose the Live run option, it will default to the current time as the scheduled start, if this has not already been set.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication Steps (if applicable)
Dashboards that group together as ‘Other’ do not show the correct runbooks list when clicked.	Dashboards	When you have six or more different results that show in a dashboard, they are grouped together as ‘Other’. Clicking on ‘Other’ should show the list of runbooks included but this wasn’t working.	Create a multi-runbook dashboard In our example we have added a component for runbook split and set the attribute to a custom field that has 6 or more options. Go into your workspace and add data to the custom field used in the above step for 6 or more runbooks. The correct number of runbooks are displayed in the list
Transition from rehearsal to live run causes Microsoft Graph integration to fail.	Integrations	Changing a runbook from rehearsal mode into live mode is causing the Microsoft Graph integration to fail with Connection failed status.	Create a normal runbook and add the Microsoft Graph integration Execute the integration in Rehearsal stage Go back to Planning stage Execute the integration in Live stage Integration should be executed successfully in Live stage

2024.9. release - July 2024

Overview

Changes to runbook-level integrations

You can no longer enable/disable runbook-level integrations during a live or rehearsal run or in approved templates. You can still use the Re-fire and Run integration button and view the Action Log. Runbook-level integration custom fields can also be added, edited and changes saved whilst in a live or rehearsal state.

For more information on Runbook-level integrations, see our Help Center article.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication Steps (if applicable)
Linked tasks link to original template in copied runbooks.	API	When you create a copy of a runbook that has linked tasks, these are still linking to the original runbook and not the newly created runbook.	When using the API to copy runbooks, it now copies the linked tasks runbooks into new runbooks.
Comms disabled in parent runbook does not disable them in linked runbooks	Linked Runbooks	When using linked runbooks, starting a run and setting the parent communication settings to off, does not disable communication settings for the child runbooks.	Create a runbook and add a linked runbook. Start a run and turn off the communication settings. Go to the linked runbook and check that the communication settings are off. These settings should be inherited from the parent runbook.
Searchable custom fields can no longer be refreshed on historically completed runbooks.	API	When a refresh occurs on a searchable custom field, we now ensure that the new data sync no longer updates historical completed runbooks.	N/A
CSV Import: partially blank custom field column causes connection lost error/invalid data	CSV	When importing a CSV file, where required fields were left blank this caused a ‘connection lost’ error preventing customers from accessing or actioning anything on the runbook.	We’ve fixed this on our side and updated our Help Center article to confirm which fields are mandatory and which are not.

2024.8.2 release - June 2024

Overview

You can now create and manage your own searchable custom fields. Searchable custom fields allow you to search for an external data source from a custom field located within the Edit Task or Runbook Edit panel. This feature is useful when needing to quickly surface and take action on data that is stored in other systems and is updated frequently in third-party apps. As a result, you can execute runbooks with up to date information, reduce the risk of errors and spend less time copying and pasting data between tools.

Data Sources

You can set up your own connection to an external data source such as ServiceNow and use our searchable custom fields to utilize the data within your Cutover runbook. Using a data source with a searchable custom field helps you get to the correct information quickly, saving time and reducing manual intervention.

For more information, please see our Set up Data Sources article in the Help Center.

Searchable custom fields

Use our new Searchable (single-select) or (multi-select) custom fields to see single or multiple updates from your data source.

For more information, please see our Set Up Searchable Custom Fields article in the Help Center.

Top bug fixed areas

The below chart outlines the top problem categories that have been resolved in this release upgrade. This upgrade included 10 bug fixes.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication steps (if applicable)
Node map not updating automatically	Task List	When using saved filers, switching between filters does not update the node map. This should happen automatically.	1. Create a runbook and add tasks 2. Save some filters 3. Select a saved filter and view the node map 4. The node map should update automatically
Selecting Other>Late causes no tasks to be found	Runbook	If the filter Other>Late is enabled, refreshing the page causes no tasks to be found.	1. Create a runbook with tasks. Schedule the runbook in the past to make the tasks late by default 2. Start and complete 1-2 tasks (should not appear when filtering by Late) 3. In filters, click Other and then choose Late. Late tasks should display

2024.7.1 release - June 2024

Maintenance release

This release contains bug fixes and minor internal improvements.

Top bug fixed areas

The below chart outlines the top problem categories that have been resolved in this release upgrade. This upgrade included 13 bug fixes.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication steps (if applicable)
Incorrectly formatted HTML added to the runbook homepage is not saving or showing an error	Runbook	When HTML is copied and pasted into a runbook homepage and then saved, the homepage appears blank as if no changes were made. We believe this HTML to be badly formatted with errors or extra brackets in the body of code.	Create runbook Copy HTML that has been incorrectly formatted and paste it in the Executive Summary using the rich text editor Save and reload the page The HTML should now appear
Folder level permissions showing list of all users	Workspace	When adding users to a folder level permission, a list of all users is displayed rather than capping at 10 and then displaying a show more/show all option.	Create folder Add permissions for 10-20 users The system incorrectly displays the list of all users and should cap the list and include a Show all option
Users unable to authenticate Microsoft Teams integration	Integrations	Users are unable to authenticate their Microsoft Teams integrations from within the Task Edit panel and are redirected to an error message.	Navigate and click on the Microsoft Teams integration task to open the task details Scroll down to the Microsoft Graph section and click Authenticate Users are taken to a new screen showing a Server Error message Users should be able to click Authenticate and then start the integration correctly

2024.6.3 release - May 2024

Integrations Audit Log

You can now download an audit log of Integrations Settings changes. The audit log will show what has been changed, who made the change and when, and all the events within Integrations settings and actions where a change has been created, updated or archived. For more information, see our Integrations Audit Log article in the Help Center.

Self serve role mapping

Global User Admin roles can now upload and manage their SAML (SSO) mappings allowing auto assignment of roles based on those mappings. User roles in third-party identity providers can now be mapped to Cutover allowing the auto-creation of users upon their first valid SSO login and the ability to purge roles. For more information, see our Upload mappings for RBAC article in the Help Center.

Top bug fixed areas

The below chart outlines the top problem categories that have been resolved in this release upgrade. This upgrade included 19 bug fixes.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication steps (if applicable)
Runbook start time not logged when created as Plan only.	Audit	If you create a new runbook and leave it as Plan only and set the time to something other than 00:00, then this is not logged in the audit log.	Create any type of runbook (‘normal’, 'dynamic', etc) Give the runbook a title Leave the runbook as Plan Only but change the time to something other than 00:00. Click Create. Go to the Audit log Select the runbook you just created In the details it should show you the start time like it does when you create a runbook with a fixed start date/time.

2024.5.2 release - April 2024

Maintenance release

This release contains bug fixes and minor internal improvements.

Top bug fixed areas

The below chart outlines the top problem categories that have been resolved in this release upgrade. This upgrade included 18 bug fixes.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication steps (if applicable)
When executing the “Create a runbook from template” action the "Updated at" parameter is updated.	Runbook	When a runbook is created from an approved template, it updates the "Updated at" date seen in the template details panel when it shouldn't.	Create or use an already approved template Now navigate to Template details → Other details → Updated at panel and make a note of the date/time shown Now navigate to Template settings and click on Create runbook from template After successfully creating a new runbook, navigate back to the source template details panel
Unable to add a Snippet Task if the template is a child template.	Snippets	When a template is used as a child template (ie: used in a Linked task in the parent template), the Snippet task type isn’t available in the child template when it should be.	Make a template. Add linked task. Choose other template for that Linked task. In child template, attempt to add a Snippet task
Comments made in older versions of runbooks are not visible.	Runbook	Comments made in older versions of runbooks should be visible but greyed out.	Create a runbook and add a comment to a task. Go to the cog menu and Save a new version. Check the runbook comments and you should see older comments but greyed out.
Template: Can't export user list when in approved state.	Runbook	You should be able to Export user list in approved template, and the option to import users on an approved template should not be available.	In an approved template, go to the User management panel. Click on More options “Import” should not be an available option.

2024.4.2. release - March 2024

Maintenance release

This release contains bug fixes and minor internal improvements.

Top bug fixed areas

The below chart outlines the top problem categories that have been resolved in this release upgrade. This upgrade included 13 bug fixes.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication steps (if applicable)
When bulk uploading, the system does not recognise that a CSV file has been added	CSV	During the bulk upload process, a CSV file was added and when you click Upload to start the process, a message was displayed with an error.	Navigate to Account Management Click create and choose bulk upload Set the users to have workspace member access Set the users to have email login Click Create
Runbook timeline Now button does not navigate to today’s date	Runbook	When clicking on the ‘Now’ button, it did not move the timeline view to show today’s date.	In a workspace, navigate to the runbook timeline view Move the timeline to show dates in the past (or future) Click on the Now button
Runbook nodemap fails to display	Runbook	When selecting the nodemap view and applying filters, the browser was unable to load the nodemap in certain cases.	Create a new runbook Import tasks from a CSV Switch to the nodemap Apply stream filters The browser should show the new filtered list in the nodemap
Inability to edit or run integrations at runbook level	Integrations	Customers were unable to trigger runbook level integrations as runbook admins.	Create a runbook integration and link it to a runbook Find a user to activate the integration in a runbook. Runbook admins should be able to run or edit the integration

2024.3.4. release - March 2024

This release contains bug fixes, minor internal improvements and UI enhancements.

UI enhancements

We’ve made some UI changes to enhance and introduce additional functionality. These are:

Workspace tabs now display different icons

Tooltips will now display where a runbook or a multi-runbook dashboard name has been truncated
Scheduling a multi-runbook dashboard now works the same as when you schedule a single runbook dashboard
Runbook table view now has a higher contrast when you hover, the ID and Name columns have been frozen, and there is improved sorting
You can no longer modify the runbook type during the duplication of a runbook with a disabled runbook type
When merging runbooks, you will need to enter at least two characters when searching for your destination runbook to be shown results
Searching by runbook ID now displays the search criteria and number of IDs being searched in the selected filters accordion
Saved views will now feature an icon that corresponds to its type:
- When you add a template, snippet or runbook to Starred
- When you save runbooks, snippets or templates in Saved Views
- When you save a multi-runbook dashboard in Saved Views

Top bug fixed areas

The below chart outlines the top problem categories that have been resolved in this release upgrade. This upgrade included 12 bug fixes.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature Area	Description	Replication steps (if applicable)
Incorrect error response	Comms	When adding a recipient within an email task type, a “not in account” error was generated which is not an expected response.	Create a new runbook with an email task type Click on email task and navigate to the “Settings” tab Add a recipient/user that contains the following roles that was observed at the time of the error (GA + Workspace Member, Runbook Admin) The “not in account” error should not be displayed on the front-end and if an error is found it should be detailed as “not in workspace” instead.
Specific characters not exporting within the CSV	CSV	When exporting runbooks from the workspace runbook list, the following: "&", "-", double quotations, “<“ and, “>” characters were not exporting correctly via CSV.	Export any runbook to CSV which contains the mentioned characters.
Global Stakeholders not able to see all list of permissions on other users.	Roles & Permissions	Users that have the Global Stakeholder role could not see the full permissions list when checking individuals permissions.	Set role to global stakeholder only Try to view the users permissions

2024.2.3 release - February 2024

Changes to mandatory fields in the CSV upload process

This release contains a change to our CSV upload process. From this version, only the Task Title is a mandatory field when uploading CSV files. All other fields are optional. For more information, see our Export and Import Tasks article in the Help Center.

New create an integration experience

We’ve redesigned the process for creating an integration and you can now access helpful links and example guides via our Developer Portal. These new guides provide the steps needed to build a custom integration with third-party systems such as JIRA, Ansible, Teams, ServiceNow and more. For more information, see our Custom Integration article in the Help Center.

Top 10 bug fixed areas

The below chart outlines the top 10 problem categories that have been resolved in this release upgrade. This upgrade included 36 bug fixes.

Notable fixes

The listed issues and their solutions are organized based on their potential impact on customers.

Problem	Feature area	Description	Replication steps (if applicable)
Linked Tasks when filtering for Searchable Custom Fields - Cutover then presents a 500 error	Linked task	When linking a task, searchable custom fields are filtered on the left side of the window. Searching for anything within these filters used to give a generic 500 error.	Note: Requires searchable custom field(s) to be set up to appear within the filter. Create a runbook within a workspace that contains the required Custom Fields. On a task, click the ellipsis(…) and select “Insert linked task(s)” In the window that appears, note the searchable/remote Custom Fields appear as filters on the left side Search for any data within these filters
CSV export not exporting the correct data for restricted Custom Fields	CSV	Custom Fields restricted to 2 or more integration task types are not generated correctly within a task export CSV.	Create a new Custom Field Within “Restrict to integration” settings, ensure the Custom Field is restricted to two or more integrations task types Navigate to a runbook on the front-end where the custom field can be used and enter a data entry Export the task list via CSV
Improve Integration error handling	Integrations	Return integration failed if the integration webhook URL is blank	Create a Custom Integration integration action item without a URL Trigger the integration
Show all permissions changes in User History Audit log CSV	Audit	Scenario 1 - For roles that were removed that are not restricted to a workspace Roles should be listed even when not restricted to a runbook or workspace Scenario 2 - For role changes where workspace and runbook are specified Roles, runbooks, and workspace should be separated to make it possible to quickly see which role corresponds to which workspace. (As an example, currently, it reads as “Assigned roles changed. Added Support Workspace Workspace runbook creator, Support Workspace Workspace stakeholder, Test Workspace Workspace member.")
Provide auditing when bulk login type has been updated	Audit	All changes via bulk upload should appear in each user’s history log.	Create 1-2 test users, assign any workspace/role and any login option. Bulk update these users via .csv, choose same/different roles but change login option.
Comms to non-provisioned, allowlisted Email Addresses	Task list	Comms should be able to be sent to any recipient, if the recipient is within the allowed list of email addresses	Create a runbook Make a comms task Try to add a non-provisioned email address to the list of recipients
Merging runbook should merge stream names correctly	Runbook	Duplicates stream names should be merged regardless of difference in capitalisation.	Create multiple runbooks with streams of the same name with differing levels of capitalisation Merge the runbooks Note that in some cases the streams were not recognised as the same and you end up with duplicates

2024.1. release - January 2024

Blank fields fix for CSV uploads

This release contains a fix for CSV uploads where required fields left blank caused invalid data. We have also made some minor internal improvements.

In 2024, our release version convention is changing. The format will consist of the year, a release number and an internal build number e.g. 2024.1.4, which can increase if we have created a patch release.
We’ve done this to help you understand what version your customer instance is on, in relation to the current version of Cutover. We hope we’ve made things better and if you have any questions, please speak to your Customer Success Manager (CSM).