Skip to end of banner
Go to start of banner

Upcoming Releases

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Below are features and fixes we anticipate will be in the next releases for JMWE for Jira Cloud.

Note: All features and fixes listed below are currently in progress and are actively being developed. We cannot guarantee that any specific update will release in the stated window, or that the release window will occur as anticipated.

You are viewing the documentation for Jira Cloud.

Contents


Version 1.2.33-ENG - Anticipated Release Date: 19 August, 2024

Bug fixes

The following bugs are planned for resolution in this release:

  • Incorrect images copied when using the ‘Copy comments to related issues’ post function - Occassionally when using the Copy comments to related issues post function to copy comments that include images, the image that was last attached to an issue would get copied, instead of the image included in the comment being copied.

  • Configurations not saved when switching between no-code and Jira expressions - In the Build-your-own (scripted) Condition and Build-your-own Validator, new configurations would sometimes fail to save when switching between the no-code and Jira expression versions of the extensions.

  • Cloning an action results in post functions with identical ID values - In some instances, cloning an Action (Shared, Scheduled, or Event-based) would result in the included post functions having identical ID values to the original post functions - even when the two post functions have different configurations - resulting in confusing or broken error logs.

  • Validations skipped incorrectly - In some instances, Validations are being skipped when the Skip validation when cloning/creating an issue option is checked, even when the triggering action is not cloning or creating an issue.

  • Incorrect destination page when creating an extension - When using the Create new function from the JMWE workflow extensions administration page, switching the value of the Project pulldown menu would still result in opening the workflow for the first project selected.

  • Broken links when testing Nunjucks Templates - In some instances, after testing a Nunjucks template, the links to more detailed information were broken and would return an HTTP error.

  • JCMA migration of Event-based actions support for missing issue events - A few events were not being migrated successfully to JMWE Cloud when using Jira Cloud Migration Assistant (JCMA), including Issue Watcher Added and Issue Watcher Deleted. These events will now migrate to an “Issue Created” event in JMWE Cloud.

  • Missing Shared conditions and Shared Validator migration warnings - Previously, um-migrated JMWE Shared conditions and Shared validators did not trigger warnings in the post-migration report if the warnings had been dismissed in previous migrations. These extensions will now trigger a warning in every post-migration report.

Version 1.2.33 - Anticipated Release Date: Late August, 2024

Enhancements

Extensions

Set issue field(s) post function added support for Object field types

The Set issue fields post function will be updated to include support for Forge Object type fields.

Build-your-own (scripted) post functions now include ‘Run as’ configuration

The Build-your-own (scripted) post function will be updated to include a ‘Run as’ configuration, enabling the post function to run as a selected Jira user instead of only as the add-on user.

Linked Issues Condition & Validator support for min/max options

The JMWE Cloud versions of the Linked issues Condition and Validator will support configurations for minimum related issues and maximum related issues, similar to the Data Center versions.

New option to ignore fields on Clear Issue Fields post function

The Clear issue fields post function will be updated to ignore (not display) non-editable fields when selecting which fields to clear.

Post function editor displays transition information

The post function editor window will now include information about which transition the post function is currently applied. For administrators managing numerous post functions, you will now be able to tell which post function you’re editing at a glance!

User notifications added to post functions

Previous to this release, notifications for JMWE post function errors would only display in Jira if the logged in user is an Administrator. This update to several post functions will enable the option to display an error message to any user.

Actions

Action data includes user audit trail

Shared actions, Scheduled actions, and Event-based actions now include additional audit data on their management screens, including the user who last modified (or created) the action, when the last edit occurred, and when/who disabled or enabled the action last.

Version 1.2.34-ENG - Anticipated Release Date: September 2024

Bug fixes

The following bugs are planned for resolution in this release:

  • Linked Issue Validator incorrect behavior - In a few configurations, the Linked Issue validator does not validate correctly, enabling the creation of other links and failing to display an error message.

  • Minimum width display issue for some post function configuration fields - A minor display issue occurs when viewing some post function configuration fields at lower resolutions or less than full width page.

  • Intermittent security issues with the Assign issue(s) post function - In rare cases, a security issue is triggered when executing the Assign issues post function.


Questions.png Questions and feedback

  • Explore exciting features, pricing updates, reviews, and more on the Marketplace.

  • Stuck with something? Raise a ticket with our support team.

  • Do you love using our app? Let us know what you think here.

Credits.png Credits

A heartfelt thank you to our valued customers! Your incredible support and feedback inspire us to improve our apps and products continually. You are the driving force behind why we create software. We appreciate your trust in !

  • No labels