Atlassian at its best!
Lots of people complaining missing basic functionality, but it's still a feature request, not a bug.
So all of them waiting for ages to get this fixed.
Also promises are done that they will be provide a 100% solution.
And what happens? The same sh** as everytime! Work is maximum 50% done, feature request is closed, Atlassian is proud to announce a new transition screen nobody needs as the main functionality is missing and for all the people really need, a new feature request is opened where the idiots of customers can start voting and waiting again.
Nobody is happy except Atlassian product management, because in there statistics it looks good because the old feature request is closed...
Moreover they don't care or react in any way to customers feedback, or why did you not answer to my comment https://jira.atlassian.com/browse/JRACLOUD-78919?focusedId=3543013&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3543013?
7645729f7e9f Maybe you want to answer at least to that one? I would be curious why did you break your promises?

I'm not sure why this piece of work has been closed as 'Fixed'? The new issue experience does not have feature parity with the old experience as Assets is excluded.

Why has this been separated out into a different ticket? The expectation from this ticket was to have all functionality from the old experience made available in the new experience?

All updates about the integration of the Assets field will be posted here https://jira.atlassian.com/browse/JRACLOUD-85466 

Is there any issue that tracks the integration von Asset Custom fields into the new transistion experience? Assets are used by a lot of my JSM customers, so I'd like to track the progress of the development.

Hello, like fc00a64f2a44 , we are using Assets fields in transition screens, and it is necessary for us to have the functionality further. As long as the Assets fields cannot be used in "new experience transition screen", the old experience must be available. From my point of view, Atlassian cannot close the ticket without support for all field types inclusive Assets fields.
It is clear, that Assets fields are not fairly supported by Atlassian. Assets fields are not supported by migration Server -> Cloud or Cloud -> Cloud. But Assets fields are the important functionality piece, which decisively influences the purchase of Atlassian product. We want to see better support for it!

We’re slowly moving users from the old experience to the new experience to ensure one experience for all of you.

We use Assets fields in many transition screens, how are you preventing our users from being transitioned to the new experience so that our processes are not broken?

91a6d4b3a588 I was already afraid of exactly this situation in June/July - please see the following 2 comments:

• https://jira.atlassian.com/browse/JRACLOUD-78919?focusedId=3470059&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3470059
• https://jira.atlassian.com/browse/JRACLOUD-78919?focusedId=3470650&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3470650

7645729f7e9f What's about your promises in July? Now, already a lot more than 8 weeks later, everybody gets the new transition screen without closing all gaps? What did you do in the mean time?

You've marked this as Closed and yet Canned Responses still are not available from the Transition Screen and not all fields are supported?  We've been waiting for months (if not years) for these things to be implemented.  What gives?  I wish my job would let me get away with marking tasks as Closed without making sure everything had been addressed first.  Is Atlassian hiring?  Sorry for the snark, but this is very troubling to see these things being ignored while we, your customers, have waited patiently for these basic things to be implemented.  Even the issue about the default being set to Internal Comments has not gone addressed.  At least give us the option to set the default behavior we want.

I'm shocked that this has been pushed through without first fixing how the default comment type is handled (https://jira.atlassian.com/browse/JSDCLOUD-14319). I've been previewing this features and have many time inadvertently transitioned an issue back to the customer without noticing that the default comment type of 'internal note' was still set, only to come back a week later and noticed the customer never received the comment.

When adding a comment to an issue, you are forced to choose between internal note and reply to customer before the comment text field appears. Why can the same not be done during the transition screen to avoid this kind of problem?

Now we'll need to warn all of our JSM agents to be aware of the comment type and remember to change it to 'reply to customer' whenever they transition an issue.