Now GA - try the new issue transition experience in Jira!

[Flavio Di Transo]

The comments jira expressions doesn't works in the new transition experience. The new feature is bvroking my validator and conditions on comments. Please, share some update documentation about Jira Expressions, please.

[Matthias Rieder]

Discovered yesterday, that asset fields now seem to be supported. 👍

Was about time.

[Darryl Lee]

Hi @Flavio Di Transo - you are probably running into what I wrote about here:

• Workflow Validators and Conditions might break soon if you use custom Jira Expressions 

Adaptavist has written an excellent guide with even more examples, which is where I stole mine, so you definitely want to check that out as well:

• Compatibility of Atlassian's New Transition Experience with Jira Expressions

[Flavio Di Transo]

Hi @Darryl Lee , you are right, but what i mensioning is another behavior.

With the new transition experience, the comment inserted in transition screen is not accesible and it's neither possible access on its properties, to check for example if the comment is internal or not.

This seems the same behavior of the attachments on tansition screen; the attachments are handled in asynconous mode in transition, because them are saved in a temporary storage when you upload it and only when you complete the transition them are stored on issue.

Like I did before for the attachments, the only workaround that I found to inspect the comment properties is using a filter that check the comments inserted in the last minute.

[S Fong]

Who can see the comments under internal note?

[Mike Boutin]

What did they do to the FONTS? The new UI has a different font.

[Monika Marko]

I am a Jira product admin in my company and I haven't turned this feature on for myself or the rest of the product & engineering org. I am wondering, however if the transition screen breaks any integrations with bitbucket. E.g. devs transition an issue after they review it in bitbucket and it automagically updates the status in Jira. In the past a transition screen would disable the automation, so we have disable them for any status except for Done, which is done manually. Maybe this is captured somewhere in all the 4 pages of comments, but if someone could point me to it, that would be super helpful. Thank you!!! 

[Fred Quintero]

Hey team! 

The last update on  Update on October 23, 2024

"(1) Support for Asset field: The old transition screens will continue until the Asset field is supported on the new transition screens."

I see for my instance it says that I will be moved into the new experience May 22,2025

Will we be able to go back to the old view? Is the plan to have Asset fields working by then?

Thanks!

[Rick Westbrock]

@Fred Quintero I think that Assets field support was already added according to https://jira.atlassian.com/browse/JRACLOUD-85466 which was closed as Fixed on 2025-04-15. Oddly there wasn't a specific comment from Atlassian on that RFE about it being resolved.

[S Fong]

Is this new issue transition experience only applicable to JSM?  I dont have JSM but why is it allowed me to turn on this new feature under Personal Setting?  

[Martin Sanchez M]

Hi!

Thanks for the update; I have a question about the update: Are there plans to implement predefined responses that agents can use when closing tickets and need to inform the customer? This option was previously available. Another point: Will an Asset field be allowed to have more than 20 objects?

Regards,

[Robert Eiser]

Hi @Arbaaz Gowher is there a way to default the "Log Work" option to be opened instead of closed in the new transition? In the classic transition view Log Work was always visible to our users if it was on a screen. In the new layout it is always closed/hidden so that the user must open it to log work. I am noticing a decline on logged work since we turned on the new transitions and I suspect this is the reason.

I understand there may be contexts where admins would want log work to default closed, but could you allow us to also default it to open at the admin level?