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

59 comments

Dwight Holman
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 18, 2024

Is there a keyboard shortcut to complete the transition? I note some others mention a shortcut that works when the comment field has focus. But IMHO there should be a shortcut that works in ANY field.

Shift+Alt+S seems to work on the old transition screen, but doesn't work on the new one.

Dwight Holman
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2024

@Yatish Madhav - I have been using the Shift+Alt+S shortcut to complete the transition dialog (on Windows) for some time. This seems to work on all Windows web browsers. Sorry I don't know if an equivalent exists on Mac and don't have one here to try.

This is not as intuitive or easy as Ctrl+Enter but faster than mousing and clicking.

Unfortunately this shortcut is broken in the new experience - backlog JRACLOUD-84777

Like Yatish Madhav likes this
Yatish Madhav
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2024

Brilliant - thanks @Dwight Holman 

Nathan Phillip Brink September 20, 2024

I had an issue where on two desktop computers, the browser used to be able to load the forms for the transition. But then it stopped working with a JavaScript error while trying to load the old experience. First one desktop browser stopped working and then the next week my other desktop’s browser stopped working. I had resorted to filling out the transition forms using my mobile phone’s browser.

Switching on the new experience avoids the client JavaScript bug, letting me transition in my desktop browser at all. So I am pretty happy that it happened to show up as an option at this time.

I do like that the new experience’s rich text editor matches the normal inline issue comment rich text editor. Keeping track of two different ways of typing formatting information (e.g., `code` for the new one and {{code}} for the old one) was confusing.

Jonas Lerch
Contributor
October 9, 2024

I had the new "experience" disabled. It was reactivated at some point. -.-

Can we get the keyboard shortcut for save back?

Can we get a setting for choosing if the message defaults to internal or customer?

Why do we have to life with those regressions all the time?

Like # people like this
Dan Heffernan
Contributor
October 9, 2024

I agree with @Jonas Lerch 

We are still having the issue with internal note being default. Switching off the new experience is only a stop gap measure and from what I understand, it's going to be switched back on towards the end of October.

Like Dwight Holman likes this
Dwight Holman
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 13, 2024

Some of my team have reported a strange "Communications Breakdown" error when using the old experience. Atlassian suggested trying the new experience as a workaround.

Has anyone else seen this?

Nathan Phillip Brink October 19, 2024

I wrote a userscript to preselect the “Reply to customer” tab for any GreaseMonkey/TamperMonkey/etc. users out there.

Like Marcel E_ likes this
Rick Westbrock
Contributor
October 21, 2024

I posted the following in https://jira.atlassian.com/browse/JRACLOUD-78919 back on 2024-07-08 but never got a response:

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.

If the "old experience" is removed prior to ALL field types being supported by the new experience then Atlassian is doing a great disservice to their customers.

@Arbaaz Gowhercould you possibly find out the roadmap for this and confirm here that our processes are not going to break by having the old experience removed before all field types are supported by the new experience? After three months I have given up on getting a response from Atlassian in the RFE, especially since another customer echoed my question on 2024-08-21.

Like # people like this
Dan Heffernan
Contributor
October 28, 2024

Looks like Internal Comment is still set as the default. Found that out this morning and there is no way to disable the new changes from being forced.

 

Edit: There is a way to defer up until 12/23/24. So just switched it back to old experience.

Anca ILE October 28, 2024

hello @Arbaaz Gowher 

Any news for the response canned to be added in a transition screen? any timeline/date?

 

(Canned responses for service projects: Agents can reuse predefined responses to instantly reply to frequently asked questions.)

thanks :) 

Like Marcel E_ likes this
Rick Westbrock
Contributor
October 28, 2024

I see this note was added at the top of this article two days after I posted my question about Assets fields:

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

Like Anca ILE likes this
Dan Breyen
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 31, 2024

Will end users be able to turn off this functionality after the rollout is finished?  Or at least turn off parts of it?  My users might break out the pitchforks and torches if they start getting messages about "Kudos for keeping things up to date"

Like Dan Heffernan likes this
Eric Dagenais
Contributor
October 31, 2024

What about that "jira-123 moved to Done. Kudos for keeping things up-to-date" at EVERY transition.. not the first one or 2... every transition.. one more popup

 

Like # people like this
Rick Westbrock
Contributor
November 1, 2024

Ugh, I got that kudos message yesterday and my immediately reaction was "I'm not five years old, I don't need a gold star for just transitioning an issue".

Like # people like this
Yatish Madhav
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 13, 2024

Thanks @Arbaaz Gowher - i am glad that Ctrl Enter now works ...

Next, Looking forward to the Canned response update and the Compatibility with Marketplace apps :)

Thank you and Atlassian

Like Dwight Holman likes this
Thorsten Letschert _Decadis AG_
Atlassian Partner
November 14, 2024

While the view now includes "Required fields are marked with an asterisk 

Joerg
Contributor
November 19, 2024

Are there any plans to let us define default values for fields on the transition screens when using the new transition experience? That would truly be a game changer.

Like Andreas likes this
Cedric Devaux
Contributor
November 20, 2024

Hello,

As someone already notices on transition screen experience with date/time customfield with the new experience is too restrictive because we are obliged to select pre-defined time value (30 min intervals) whereas previously we are able to enter exact time.

For me, it's very important to declare exact time in the incident for example because this information is useful to analyze later in a post-mortem.

Moreover the old display was very clear with a calendar at the top and below time, in the old version you can select directly "Today" and value is automatically enter current date and time when you click on button

Date Time Experience.png

I don't  understand the reason to change view whereas old version was very useful.

Like # people like this
Rick Westbrock
Contributor
November 21, 2024

Have you tried entering a time manually? The new experience looks awfully similar to the Planned Start field in JSM which while it does have the same drop-down for time also allows the user to key in a time manually.

Like # people like this
Mario Cid Cespedes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 26, 2024

Looking forward to use Canned Responses in a transition screen. 

Like Joerg likes this
Cinthia Tonche
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 26, 2024

Hey hola chico@s


 

Nanda November 28, 2024

I just enabled both New issue transition experience and Quick search smart queries

 

Excited and Eager to Experiment the new capabilities and provide feedback.

Joel Charlebois
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 3, 2024

Regression issue: focus used to be on first field in transition screen. This is no longer the case. 

Like Jared Colker likes this
Birger Robrecht [avono AG]
Contributor
December 8, 2024

JRACLOUD-78919 has been closed, but there is still no support for asset fields. :( It's a bit like the car has been built, but it works only on straight roads within city limits.

Like # people like this

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events