Summary

Surface full, meaningful details for 3rd‑party post‑functions (e.g. JMWE) in the new workflow editor’s transition view.

Description

Current behaviour

In the new Jira Cloud workflow editor for company‑managed projects:

• Post‑functions from Marketplace apps (for example, JMWE – Jira Misc Workflow Extensions) appear under the “Perform actions” section of a transition’s rules panel.

• For these 3rd‑party post‑functions, the transition view only shows a generic description/label (e.g. a generic “JMWE post‑function” entry).

• To understand what each post‑function actually does and how it’s configured, an admin must click into each rule individually.

• This makes it very difficult to see at a glance what each 3rd‑party post‑function is doing, and safely reason about the order and combined effect of many post‑functions on a single transition.

In the old workflow editor, admins can see much richer text describing each post‑function on a transition, which makes the workflow behaviour far more transparent.

 

Expected  behaviour

When viewing a transition in the new workflow editor, admins should be able to:

• See clear, meaningful display text for each 3rd‑party post‑function (e.g. JMWE rules) in the transition’s rule list (under Perform actions), without having to click into each rule.

• Quickly understand, at a glance: What each post‑function is doing (e.g. which fields are updated, which conditions/expressions are applied). In what order they run.

• Have an experience that is functionally equivalent to the old editor for inspecting and maintaining complex transitions with many Marketplace post‑functions.

The customer is not asking for new rule capabilities from JMWE or other apps, but for the new editor UI to surface the same level of descriptive detail that the old editor shows.

Why this is important

• Some customers have many 3rd‑party post‑functions on a single transition (JMWE and other Marketplace apps).

• In these cases, the new editor’s generic entries make the transition view feel like a “mystery box”: You can see that rules exist, but not what they actually do, unless you open each one and try to remember its position while you inspect the next.

• This significantly slows down: Workflow maintenance and troubleshooting, Safe refactoring of complex workflows, and Onboarding of new admins to existing workflows.

The risk is particularly high for larger or Enterprise‑scale customers:

• The reporting customer is a smaller business, but they point out an Enterprise‑licensed company with 10,000+ users preparing to move to cloud under the new licensing policy.

• That environment has dozens of 3rd‑party post‑functions across workflows, and admins will face the same issue of not being able to understand behaviour at a glance in the new editor.

With the deprecation of the old workflow editor planned, this visibility gap becomes critical: once admins lose access to the old editor, there will be no good way to inspect and reason about complex 3rd‑party post‑functions directly from the UI.

 

Workaround

• For now, admins can keep the old workflow editor as their default editor, and open workflows in the old editor when they need to see full details of 3rd‑party post‑functions.

• This workaround is temporary and will no longer be available once the old editor is fully deprecated.