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?

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.

My team have been impacted by another aspect of this change that may not be obvious to Jira admins. The new experience broke some of our ScriptRunner workflow validators that check rich text fields.
7645729f7e9f has noted this recently in Changes affecting workflow validators and post functions on the new issue transition experience
If you have validators or post-functions interacting with rich text fields - you should read this.

It is good to see Atlassian trying to make Jira more consistent (though not everyone appreciates this specific change). It is disappointing that Atlassian have (again) degraded keyboard shortcuts as part of a managed product change. The old transition screen allows the Update button to be triggered by a keyboard shortcut, but the new screen does not. When will this be implemented in the new transition screen? Why doesn't your development process cover keyboard shortcuts (usability) in feature work? Do your product managers care about user experience?

I join fc00a64f2a44  in his request: "Please confirm that the old transition experience will not be removed until after all field types are supported in the new experience. As part of our migration from Remedy to JSM we created a lot of transition screens which require Assets fields so if the old transition experience is removed before Assets fields are supported by the new experience that will break a huge amount of flows for our IT service desk team and make the product nearly unusable for our agents."

Maybe I missed something, but we CANNOT use the new transition experience if all fields are NOT take in account (especially Assets). Lot of validation done on workflow side on Assets field.

Hey 3f6387e75402 

There is a feature request for those dumb defaults (internal vs public):

https://jira.atlassian.com/browse/JSDCLOUD-14319

Please vote

Hi 7645729f7e9f,

I would like to note that in the new experience, it's not ideal that "Internal comment" is the default for service management projects. As a result, when we close our tickets, the user doesn't receive a public comment. I had already reported this issue during the beta version but haven't received any response. I suggest that there should be an option to require a public comment when closing a ticket.

Hello 7645729f7e9f 
How can I know when this feature can be used in my org? Currently, I see that the transition screens shows the wiki codes(/,* etc) instead of styled fonts.

Please let me know

Please confirm that the old transition experience will not be removed until after all field types are supported in the new experience. As part of our migration from Remedy to JSM we created a lot of transition screens which require Assets fields so if the old transition experience is removed before Assets fields are supported by the new experience that will break a huge amount of flows for our IT service desk team and make the product nearly unusable for our agents.

Hi 18ff56543dcf, thanks for your comment.

The reason we automatically will revert to the new experience is that we aim to close all the missing functionality/field support by that time frame. However, as called out in the community post, you, as an admin, can reach out to support if you'd like to be on the old experience for all users on your site until we achieve that state.

As for your other questions, I'd love to chat with you to understand them better and in detail. Can I request you set up a time for us to chat sometime soon here? Let me know if none of the days/times work for you  

7645729f7e9f 
I've tested the new feature, but disabled it directy again as there are actually to much upcoming improvements & changes mentioned in Now GA - try the new issue transition experience i... - Atlassian Community missing, which are essentielly needed for our workflow.
After disabling the new feature, it told me that I will change in 8 weeks automatically to the new feature.
So my question is: Do you have fixed all open improvements & changes until then? Because otherwise we'll have a big problem if that features gets enabled automatically for us. I would prefer to decide it on my own as a admin and not automatically by you.

Another question:
Is there any plan to get the change to define which fields are shown on the transituation screen?
We have some fields which I can't activate as mandatory for the whole workflow, so they are just mandatory for some transitions. Because of that that are not shown on the screen, so I get an error, have to step back to the view screen, enter the value to do afterwards the transition.
In Data Center I could design the transition screen on my own, why not in cloud?

Comments on service projects will default to internal visibility

Agents in my ITSM project are finding this quite annoying.  They want to share information with the customer as default, not hide it.
They transition a ticket, add a comment, click update and then realise it's defaulted to internal so have to edit and update it again.

A parameter setting per project would be useful so I can decide if the default should be 'internal' or 'reply to customer'.

+ looking forward to seeing canned responses on transition form

Will the new experience also solve the issue that:

1. you can't add attachments to the issue-transition-screen which are already in the ticket?
2. you can tag someone like in a normal comment, so without having a long accountid in the text?

Thanks in advance for your reply.

Any update on the ETA for implementation? Or can we still be invited to the AEP for this?

When is this targeted for release? Just looking for a general ETA.  I've never seen a ticket actually move out of gathering interest, so just trying to manage expectations on when this will be actually available.  Thanks!

Arbaaz Gowher

This Calendly URL is not valid.

also: When will users be able to add attachments on transitions finally?

Hi all,

I'd like to see the new experience to work just like how Forms work in Service Management. I could create fields with richer information and descriptions and with conditional formatting and then link those to a simpler Jira field. Or just have a simple confirmation checkbox without having to create a new Custom field for each and every one of those.

Thanks

This is great news that you are modernizing the transition screen!
May I ask when you think you'll be able to release this though?
Q3? Q4? Next year?

Same here!

I just want to add, that it's even not possible to add attachments to the comment in this screen.

It always seems so jarring and backwards when I run into the Comment box in this screen and it just doesn't work the same. 

I'm using this in Jira Service Management projects. This is the step where I'd like to add a message to a customer to let them know I'm closing the request (thank them for their time, let them know how to re-open the conversation). With the comment box in this old issue transition style: 

• I can't add a Canned Response.
• I can't just copy the canned response I want and paste it since formatting, hyperlinks on text, and horizontal rules go missing. 
• I can't quickly add hyperlinks back in, since adding a hyperlink takes multiple steps (ctrl+K to add link leaves the text selected, not the "http://example.com" that I need to replace with the URL). 

I'd like to give my customers a consistent communication experience, but I'm not getting the consistent UI experience to provide that with. 

When is it done?

Any news on that when users finally receive a modern transition screen?

This is a security matter. 

In a secure environment, data is visible on a need-to-know basis.  Defaulting comments in transition screens to visible-to-customers is a guarantee that someone is going to slip and cause a problem.

Come on guys, this issue disrupts the whole great Jira experience!

Selecting from a custom multi select field with the old view is awkward and not user friendly, also unreliable.

Please give to this issue a higher priority!

Will this render also apply to include history

I'm not able to perform quick search for multi-select field on transition screen.

It is possible in view screen.

The ticket: JSDCLOUD-13253 Asset fields are shown differently on the Create Issue screens vs. transition screens - Create and track feature requests for Atlassian products should be related.

any new updates?

Not only it is inconsistent and counter-intuitive for people not used to old Jira markup, it also sometime breaks rendering of elements like /status or admonitions (/info|/warn|...)

Sometimes I really begin to regret choosing and advocating use of Jira, when important and deal-breaking features can sit for ages in the backlog.

The comment field in the new issue view and the incumbent transition screens now show 2 different generations of Jira. Please update the transition screens too.

Definitely priority of this issue shoud NOT be "low"!

This can significantly improve the UE for both technicians and end users.

I think these should all be related:

• https://jira.atlassian.com/browse/JRACLOUD-80133
• https://jira.atlassian.com/browse/JRACLOUD-74797 (Now closed as duplicate)
• https://jira.atlassian.com/browse/JSDCLOUD-631

Having different renderers for the comments box in different parts of the system is stupidly inconsistent... I really don't understand why the new renderer has only been half implemented?

With the introduction of Canned Responses, users really want to be able to add Canned Responses during transitions so the new editor is a requirement for that. I hope that the demand there will increase the priority of this issue.

Can you say why this ticket set as priority low?
As long as this screen is not using the new WYSIWYG editor, you cannot consider the rollout of the editor as being completely done.

The current situation is very incoherent and frustrating.

This should not have the priority low. 

You bring new features like canned response and no one can use it while closing his tickets over the transition screen..

Any update here?

This is related to https://jira.atlassian.com/browse/JSDCLOUD-631.

The new view needs to be added to Transition screens as well. 

Biggest problem here for me is the wiki style Renderer,
I use certain text fields on the tickets that can be filled in via Tranistion screen.
But due to differences in the system, i cannot add an image inside the text box on the transition screen. 

Any update here?  This is more important than create screens since there is no workaround.

this stuff should be high priority, come on Atlassian!

I use a multiline text field that needs to be filled in on transitioning to resolved status. 

When the field is filled in on the transition screen, my users are not able to copy paste images into their text, which causes much frustrations. 

However, on the actual field in the ticket, it's perfectly possible to do so. (new issue view on issue vs old issue view on transition scren)