Feature Release - JMWE for Jira Cloud 1.2.35
Our team is thrilled to announce the latest release of JMWE for Jira Cloud. This release includes a completely reworked Get Started app page, further UI updates, and several Bug fixes. The Get Started page has been reworked with additional use cases, including demonstrations of how to create each. Of special note is the new One-click Setup feature for JMWE that will create an Event-based action for you based on some of the use cases showcased there.
Contents |
---|
App Administration
New ‘Get Started’ including One-click Setups!
The Get Started page for JMWE Cloud has been reworked to include better navigation to the workflow editor and primary JMWE administration pages, as well as new Use Cases for both Event-based Actions and post functions. Most exciting is the new “One-click” setup of featured Event-based Actions! Clicking the Apply use case button (pictured above) will open the Event-based Action editor with the configuration for that Use Case already applied. Just check that the configurations are correct, name your Event-based Action, and click Save!
JMWE menu options in Jira board, issue, and project views
Shortcuts have been added to several native Jira views, including the board (pictured, right), the project sidebar, and the Action menu in the Jira issue view. These shortcuts will take you to the Workflow editor for the board, project, or issue, so you can update or create JMWE extensions!
Enhancements
Extensions
UI updates for various Conditions and Validators
A few more extension configuration screens (conditions and validators) have been updated with our new UI! Configuration options have been clarified and made more consistent. The following extensions have been updated:
Conditions
Validators
Bug fixes
The following bugs are fixed in this release:
Copy issue fields missing configuration options
The “Value before transition” option was incorrectly dropped from the Copy issue fields post function during its redesign. This option has been restored.
‘Add to Shared Action’ inconsistent behaviors
In some circumstances, using the browser’s Back button when saving a Shared Action would create a duplicate of the most recently added post function within the action; this would most often happen when using the Back button after adding a post function with the Add to Shared Action button. This has been resolved.
The Add to Shared Action dialog was allowing for Name values with only spaces, creating display problems within the Shared Action. You will not be able to add an extension to a Shared Action unless you give it a name!
Linked Issue Condition does not evaluate correctly
In some instances, the Linked Issue Condition was not correctly verifying the requirements of the Condition against its target issues. This has been resolved.
Invalid warnings for JQL expressions after migration
After performing a migration to Jira Cloud, some extensions with JQL extensions were incorrectly flagged as having errors in their JQL; this included the display of error warnings in the extension configuration page. This has been resolved.
Display issues on some configuration fields
Some configuration fields were being cut off on smaller displays. This has been resolved.
Feature Release - JMWE for Jira Cloud 1.2.34
Our team is thrilled to announce the latest release of JMWE for Jira Cloud. This release includes significant UI updates to several post functions as well as…
Due to a recent bug, some Validators may behave inconsistently, especially when using the option Skip validation when cloning/creating an issue. Validators created after the release of version 1.2.32, or any Validators that are updated and saved after release, will not experience this particular issue.
If one of your Validators is not working as expected, after the update to 1.2.32 has been applied, simply open the Validator, make a small change and save it, then change it back. Any issues should be resolved. If issues persist, please contact Support and open a ticket.
Contents |
---|
Enhancements
Extensions
UI updates for various post functions
Several more extension configuration screens (post functions, conditions, and validators) have been updated with our new UI! Configuration options have been clarified and made more consistent. The following post function screens have been updated:
Post functions
Conditions
Validators
Additionally, all deprecated post functions have also been updated with our new UI. These post functions remain unsupported and should be migrated to their new versions as soon as possible!
These changes are organizational and cosmetic only - no configurations options have been removed nor do you need to update any existing post functions!
Transition information added to post function editor
The editor screen for all post functions has been updated to include the transitions on which the post function has been applied. This includes both transition and project information.
Script editor UI updates
The script editor used throughout JMWE (for Nunjucks and JQL scripts), including better formatting and automatic line wrap for longer scripts.
Bug fixes
The following bugs are fixed in this release:
Copy issue fields post function incorrectly displays validation errors
In some instances, the Copy issue fields post function displayed validation errors for selected fields. This has been resolved.‘Max issues’ configuration allowed invalid values
For post functions that included a ‘Max values’ configuration option, the validation of that field allowed for invalid values, resulting in error messages during execution. This has been resolved.Display issues with ‘Issue Transitioned’ multi-select
The pop-up window for selecting multiple status values in the Event-based action rule builder was not displaying multiple selected values correctly. This has been resolved.‘Recipients' warning display issues
The ‘Recipients' warning box in the Email issues post function configuration screen was displaying incorrectly. This has been resolved.Scheduled action list has display issues
The Scheduled action administration page had a few display issues with overlapping text and icons. This has been resolved.Shared action ‘Delete’ button
In some instances, the Delete button was active for Shared actions that were currently in use (added to transitions). This has been resolved.