---
title: "Release notes February 2026"
canonical: "https://support.appfire.com/space/CMJC/2857566448/Release%20notes%20February%202026"
format: markdown
---
> Macro (aura-html)

**Release date**: 2/5/2026

Our team is thrilled to announce the latest release of Configuration Manager for Jira (CMJ) Cloud.

---

# Enhancements

## JMWE Workflow Support

Configuration Manager for Jira Cloud now supports the deployment of workflow elements from** **Jira Misc Workflow Extensions (JMWE). 

During deployment, CMJ Cloud can read JMWE’s internal workflow logic and safely synchronize those configurations with the Destination site. It updates system-generated logic where needed for consistency, while intentionally preserving any custom scripts or JQL already defined on Destination, so existing customizations are never accidentally overwritten. Post-functions are created and configured as expected, but script-like inputs on the target remain untouched to avoid disrupting local behavior.

> 📝 **Behavior limitations**
> 📝 
> 📝 Some post-functions, such as Slack-related or shared action functions, are migrated as configured, but external references are not resolved during deployment.

## JSU Workflow Support

Configuration Manager for Jira Cloud now supports the deployment of all workflow configurations (9 post-functions, 2 conditions, 1 validator) from Jira Suite Utilities (JSU).

## Migration to Forge

Configuration Manager for Jira Cloud has moved to the <u>[Forge](https://developer.atlassian.com/platform/forge/)</u> framework.

> 📝 **Connect End of Support**
> 📝 
> 📝 - Atlassian has <u>[announced](https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps)</u> the end of support for the Connect framework in late 2026.
> 📝 - Appfire recommends upgrading the Configuration Manager for Jira Cloud to the Forge version to stay current with future enhancements and security updates.

---

# Bug fixes

The following bugs are fixed in this release:

## Snapshot creation

Fixed a bug where a snapshot could remain in the *In Progress* status if CMJ failed to create it.

## Deleted projects

Fixed a bug where data for a deleted project in a snapshot could become unavailable after creating a new snapshot version.

---

---