Version 41.0 Release Notes

Moovila Version 41 was released on September 18, 2025, EST. The following updates are available in this release: 

ConnectWise Integration Custom Status Updates: Updates to ConnectWise Custom Status functionality will become available in waves beginning the week of September 22nd. Users will be notified prior to the activation of their enterprise. Find videos and more details about ConnectWise Custom Statuses in the release notes below and via the following articles:

ConnectWise: Custom Status Mapping

ConnectWise: Custom Status Basics
 

• General Interface Updates:
  ​

  • There will no longer be a status-to-status mapping, rather a selection of how to treat each ConnectWise status. These will now be called "status categories”. For each status in ConnectWise, the integration admin will define the associated category. These status categories in Moovila drive business rules in Critical Path engine, percent complete calculations, resource capacity metrics, etc.​

  • Each Project board will have an individual mapping to apply all statuses to an associated category. To ensure Moovila operates properly with various business rules:​

    • For Task Statuses- A status MUST be mapped to a “Not Started”, “In Progress”, and “Complete” state.​

    • For Project Statuses- A status MUST be mapped to an “Planning”, “In Progress”, and a “Complete” category.​

  • A “Default” status within each category (that statuses are applied) will be required. The first status that is dragged into the category will be marked as default, but can be changed if needed.​

  • There is no longer an explicit selection for a “Default” status to be used if something isn’t mapped as they previously did. The default will ALWAYS now be associated to the Not Started Category for tasks and In Planning Category for projects.​

  • Any new status that is created and has not been explicitly set to a category will be mapped to the “Planning or Not Started” state (depending if it’s a project or task status type).

  • Project Board mappings has been altered for a cleaner experience to allow mappings per board (individual modals vs. consolidated on a single screen).​

    • Project Boards will now have individual row mappings, and the associated mappings can be accessed by either “Add Task Status Mapping” (new customer or first time configuring after roll-out) or Edit Status mappings (after the new mappings have previously been saved).​

    • Default Project Boards will still be set and one will be required (to know which status group should be the default when creating new projects/tasks) Only one can be set as the default.

• ConnectWise Interface Mapping Changes-Project Boards & Task Statuses:

  • Statuses will be dragged/dropped to the associated “Category” mapping.​

  • Defaults can be selected for one status within each category mapping.​

  • Validations will prohibit project board mappings from being saved without all the required categories (Not Started, In Progress, and Complete).​

  • All unmapped statuses (Either previously were not explicitly mapped or a new enterprise, will have those statuses in the “Not Started” category).​

  • Existing clients will have the mapping pre-populated based on the existing status mappings. “Category.”​

• ConnectWise Interface Mapping Changes - Project Statuses:

  • Similar to task statuses, Project statuses will be set in the same manner. This is ONE list for ConnectWise.​

  • Statuses are dragged/dropped to the correct categories and the Planning, In Progress, and Complete categories must have at least one status included.​

  • Defaults work in the same manner, and validations also occur on this page prior to saving to ensure the correct mappings.​

• Project Statuses:

  • The statuses available for selection on a Project will be the single project status list that is available in ConnectWise. (Non ConnectWise clients will see the same 5 statuses that were available prior to v41.0).
    ​

  • Project Status will is also displayed in the Portfolio View with the associated status and category.

• Task Statuses:

  • The statuses available for selection on a Task will be based on the task status group that is applied on the task. This will always correlate to the statuses available on the Project Board. 
    ​

  • The statuses available are only those that are available within the Project Board itself. The statuses will be displayed along with the “category” icon.​

• Filtering:​

  • Filtering - Custom Status filter will be available along with the Status Category filtering.​ Users can filter on a specific custom status and filter on the broader category (to show all custom statuses that are mapped to “Not Started” as an example).

• Grouping:​

  • For the Groupings, users will also be able to group by either Custom Status OR Status Category.

  • Within Grid Views & Kanban, as users can drag/drop tasks between statuses, additional logic is included for what is allowed from the front end.​

  • Within the Grids & Kanban, users cannot drag tasks between DIFFERENT task status groups.​

  • Drag/Drop is not available when grouped by status category.

• Copy/Paste Statuses:​

  • If a user copies a status and attempts to paste into a DIFFERENT status group, the default status for the associated category will be applied. If a status is not available in the paste group mapped to the same category, the default for the group will be applied.​​

Non-Custom Status Updates:

• For customers that do not have custom statuses enabled, there are slight differences in how they will now see this detail.​

  • Task Details – Task details now has the status name and icon below the task name (to allow room for those with custom statuses).​

  • Project Portfolio- Status icons are available beside the project status name.​

  • Task PowerGrids- Status name is also now displayed along with the status icon.

Miscellaneous Updates:

• French language is now available for Moovila. Users can now choose French as their default language. This can be done via the More Options menu in the left navigation, then accessing User Interface Preferences.

• Timesheet – An issue was resolved where the enterprise time-zone offset was not being applied correctly when looking at time entries that had previously been edited.​

• Resource Capacity- An issue was resolved where filtered users were being applied to new dashboard panel creation (aka when a user was filtered down in the “Users to Include”selection, those filters were incorrectly being applied to new panels).​

• Task Dashboard – An issue was resolved where task details were opened within a dashboard panel, and the dashboard layout view was reverting to the first layout section.​

• General Dashboards- Dashboard security checks are now in place to determine if a user should get a specific panel based on permissions to no longer create those panels automatically from template dashboards (example- if a user does not have the risk register permission, but a template dashboard is applied to risk panels, those panels will not be created for that user).​

• Power Grids- An issue was resolved where the last column value in a Power Grid was unable to be copy/pasted.​

• Templates- Fields not applicable to templates are no longer displaying calculated values( examples- scheduled balance fields, hours logged and billable hour fields, status, etc).

Hotfixes and Minor Releases​

• 9/22/25 (Hotfix): This is an update in preparation for the upcoming deployment waves of ConnectWise Custom Status.

• 9/23/25: This minor release contains additional changes to support upcoming ConnectWise custom status functionality.

• 9/25/25: This minor release is the ConnectWise container’s update to permit custom status integration. 

• 9/25/25 (Hotfix): A series of hotfixes were performed on this date, updating the following functionality:

  • Inclusion of an additional metric to help with determining how long ConnectWise projects wait to begin syncing after the sync is requested.

  • Resolution of an API issue with queries to AutoTask failing if there were 500+ parameters in the request.

  • Update to the ConnectWise configuration to add verification that a project board is marked as the default.

  • Addition of a new backend endpoint to archive logs from Amazon, and send an updated config to the data warehouse. 

• 10/1/25: This minor release contains the following updates:

  • Adjustment to how historic request logs are purged.

  • Update to components of the ConnectWise CustomStatus workflow in the ConnectWise configuration to improve the experience.

  • Resolved an issue that was causing a ConnectWise config wizard save error to appear when the user double clicked the Next button.

  • Resolved minor ConnectWise sync issues and ensured the proper loading of Smart Schedule.

• 10/2/25 (Hotfix): This hotfix is an update to prevent the creation of duplicate custom status sync records.

• 10/7/25: A series of minor releases were made on this date, including the following:

  • An issue where task descriptions were cut off from exporting task dashboard panels has been addressed.
  • File formats when exporting from Power Grids or dashboards will now be .xlxs version instead of .xls.
  • An issue in Halo API logs where appointment types were showing unknown in the "subject" column has been addressed.
  • The Halo configuration permission checks to also validate against the required "scoped". If required scopes are missing they will now display in the same manner as missing permissions.
  • The Halo integration now verifies the project’s start date is before the end date when importing in to Moovila.
  •  Additional scopes were added to the permission check in the Halo integration.
  • Teams are properly created in the Halo integration when the configuration is saved.
  • A safety check is now performed when implicitly deleting tasks/tickets in the Halo configuration.
  • API logs functionality updated to show appointment subject properly as well as record Halo API requests for authentication tokens and settings.
• 10/8/25 (Hotfix): This hotfix resolves an issue that resulted in errors when syncing a projects without set due dates in Halo. It also addresses a validation issue that allowed for a project synced with Halo to have the start date cleared in Moovila.
• 10/10/25: This release features many points of functionality including:
  • Custom Status values are no longer returned for Projects and Tasks in the API.
  • Performance improvements in the loading of the Capacity area of the Moovila app.
  • A race condition in the task search has been resolved.
  • Backend enhancements were applied to pave the way for future functionality.
  • Updates have been applied to the way in which ticket types are set on ticket updates from Moovila to ConnectWise. This resolves issues updating tasks when an enterprise has changed the board assigned to a project.
    • If the ticket’s type is on the project board, send it with the ticket update.
    • If the ticket’s type is not on the project board, but can be name matched with a type on the board, send the updated type and write a User Facing Log.
    • If the ticket’s type is not on the project board, and can not be name matched with a type on the board, clear the type on the ticket and write a User Facing Log.
• 10/13/25 (Hotfix): This hotfix resolves an issue that occurs when ConnectWise returns a 404 for project boards that actually did exist, which was causing duplicate project boards to be created in Moovila.
• 10/14/25: This minor release includes several backend fixes and enhancements. These include a resolution to an issue wherein tasks were automatically closing due to email notifications (email server testing links during virus scanning), and the inclusion of two new endpoints.
• 10/15/25 (Hotfix): This hotfix updates the ConnectWise container to add an endpoint which deletes duplicate task custom status groups. Now when a task is marked closed in ConnectWose, the task in Moovila is properly marked at 100% complete. Additionally, logic was added to stop the project sync if Moovila's call to ConnectWise returns that time work types aren’t found. This call should never return a 404 and if it does, we know ConnectWise might be in an outage window. Instead of continuing on with the sync and getting back 404 responses, the sync will stop.
• 10/17/25 (Hotfix): This hotfix resolves an issue that resulted in the sending of task due date changed email notifications each time a task was changed, even when the task due date was not changed.
• 10/22/25 (Hotfix): This hotfix resolves several outstanding issues, including:
  • In the ConnectWise integration, an update was made to provide additional detail (project name) when a sync is stopped due to the time/ wage type call returning a 404. 
  • In the application's back end a validation was added to prevent the save of a project if the project status group’s enterprise GUID or default task group’s enterprise GUID doesn’t match the project's enterprise GUID. If this occurs, the project add or update will not be successful. This sets the stage for an additional fix coming soon.
• 10/24/25: This minor release contains infrastructure improvements for ConnectWise and Admin app enhancements.
• 10/28/25: This minor release tests an infrastructure change that will be implemented in a later release. A second minor release on this date adds the functionality to disable ConnectWise webhook callbacks from within ConnectWise. This will be done prior to purging enterprises that have configured the ConnectWise integration.
• 10/31/25: This minor release includes a fix to immediately update task hours in the Critical Path Engine when time is logged to a task and updates for internal reporting in the data warehouse (project outside system and custom statuses) have been added.
• 11/4/25: This minor release contains support for real time sync of schedule entries into AutoTask (AT service calls still sync via the regular sync interval).  The backend deployment contains prep for new project percent complete calculation that will be available in the next Moovila release.