Changes affecting workflow validators on the new Global Issue Create modal

[#1]

Hello Jira Community,

As communicated in our previous post, we began deprecating the old Issue Create experience starting in June 2022. And we’re happy to share that as of July 04, 2022, 99.3% of all our users use the new Issue Create experience.

While we get to 100% migration, we’d like to inform you that you may need to make changes to your existing workflow validators for the create transition based on the old Global Issue Create modal for applications like ScriptRunner and JMWE. Else, the validators will stop functioning when 100% of users are migrated to the new Global Issue Create modal in December 2022.

This is due to the shift from PlainText representation on the old Global Issue Create modal to ADF (Atlassian Document Format) on the new Global Issue Create modal for custom fields: Multi-Line Text Field, Message Edit Field

You can check out the public-facing bug ticket for further technical details. You can also refer to the Jira Expression Framework documentation on Working with JSON and RichText constructor from ADF Map, in addition to the changelog entries on the Jira Platform Developer portal to support these changes. For further support, please leave a comment on the public-facing bug ticket or raise a support ticket.

Thank you,
Arbaaz Gowher
Product Manager, Jira Cloud

[Taranjeet Singh]

Thank you for sharing the information!

[David Fischer]

@Arbaaz Gowher ,

I still don't understand why the Jira Expressions engine cannot do exactly what you are recommending on its own, instead of forcing customers to make changes on every Validator.

The Jira Expressions engine could detect that it has received a Map or a string for a multiline text field and automatically return a Jira Expressions RichText object instead of the Map for system fields (description, environment,...) and return a Jira Expressions string for custom fields.

Also, the documentation at https://developer.atlassian.com/cloud/jira/platform/jira-expressions-type-reference/#richtext is insufficient, as it describes how to handle custom fields but not system fields. For system fields, outside of the new Create experience (e.g. on a regular transition), the Jira Expressions engine will return a RichText object, not a Map nor a string, which breaks the code snippet provided.

Please reconsider https://jira.atlassian.com/browse/JRACLOUD-78502

David

[Arbaaz Gowher]

Hello @David Fischer,

Thank you for your comment. Upon further investigation, we have confirmed that the system fields have no contract changes from RichText to Map object. Jira Expressions Engine and Jira Issue Create V3 API both have the values stored in system fields as RichText. I have updated the above post accordingly.

As for why Jira Expressions Engine can’t implicitly handle the conversion of the validators to work on the new GIC, Atlassian is working towards deprecating Wiki Markup in favour of ADF (Atlassian Document Format). So adding support for Wiki Markup in Jira Expressions Engine would again be a temporary fix, only to be removed again shortly.

We understand the effort involved in users having to rewrite their validators but this would go a long way in maintaining a uniform experience for customers having to write validators in the future using a single syntax.

Best,
Arbaaz

[Rich]

How do we know that the change has been made to our instance?

[Houssein Barkallah]

Thank you for this update