[Feature Release] Assets custom field now supported in the new issue transition screen 🎉

[#1]

Hello Atlassian Community,

We’re excited to announce that Assets custom fields are now fully supported in Jira’s new and improved issue transition screen!

🔧 As part of the Jira platform’s recent update, the issue transition screen received a long-overdue facelift—bringing a refreshed look and feel, improved performance, and improved field behavior aligned with Atlassian’s latest design standards. This paves the way for dynamic and more powerful field experiences going forward. Read more about the new transition experience here.

In addition to enabling Assets field support in the new transition screen, we’ve also refined and aligned the field’s behavior with other experiences across Jira, ensuring a smoother and more consistent experience.

🚀 Assets custom fields are now available for you to opt-in and try out on the new issue transition screen!

Access to the new feature will happen in two stages:

1. Before 30 Jun 2025 (Optional Access): If you’ve opted in, you can utilize the assets custom field. If a you have not opted in, you can now activate the feature at an individual level for testing. Once you are satisfied with the feature, feel free to contact our team for assistance in enrolling all your team.
   If, after enabling it, you still cannot see the new issue transition screen, please reach out to our support team for help.

2. After 30 Jun 2025 (Default Access): If you have contacted us to disable modern transition screens, we will re-enable the feature for you on 30 Jun 2025.

   Please note that we are excluding sites affected by this JAC, which is a breaking change related to the modern transition screen. Please follow the steps outlined in this guide and update your validators. Once you have implemented the fixes, please contact our support team to enable modern transition screens.

👉Please keep an eye on this announcement for more details related the modern issue transition screen

We’d love to hear your feedback—try it out and let us know what you think!

[Susan Hauth _Jira Queen_]

Whooaaa Hold the horses here.   Many of us have requested that the new issue transition screen be turned off because of the JSM default to internal comment which will have a disastrous effect on many organizations.   We are waiting on this JAC:  Need customisation option to set default for comments (Internal Comment and Reply to Customer)  to be resolved as there is no workaround.

But you are now giving a new drop dead date of June 30 2025 and yet this JAC Need customisation option to set default for comments (Internal Comment and Reply to Customer)  has NO delivery date other than some vague "next quarter".

PLEASE ensure that the new issue transition screen is not put in place UNTIL after this JAC: Need customisation option to set default for comments (Internal Comment and Reply to Customer)  is resolved!

[Rick Westbrock]

At least they waited to force the new transition experience until Assets fields were supported, initially that wasn't the case as I recall. JSM seems to be the neglected child with new features lately as the granular permissions for editing workflows doesn't include JSM service projects.

I posted to @Jehan Gonsalkorale in that JAC about the deadline since I wouldn't think it should apply to customers waiting for that JAC to be delivered (which was supposed to be in "several months" as of March 3).

[Jehan Gonsalkorale]

Hi @Susan Hauth _Jira Queen_ ! We are working on a toggle in product settings where you can set the default for your instance. In the meantime, there is an EAP to have us change the default for you (click on this link to sign up for it: https://earlyaccessprogram.atlassian.net/servicedesk/customer/portal/462/group/497/create/987). 

And hello @Rick Westbrock Good to see you here! We are working on the toggle, we just had to get the dev team to finish up their planned work. I'd also recommend you sign up using the link above and your transition screen comments will default to external and then you'll be able to use the toggle once it's available. 

We are expecting this toggle to become available sometime around June/July, but if you sign up we'll change the behaviour on your site in a few days (and it will work with the new transition screen experience). 

Does that help? 

Absolutely understand the frustration here. 

[Susan Hauth _Jira Queen_]

Hi Jehan,

Thank you for pointing us towards the EAP program.  But imho I have no idea why you are pushing forward with this default to "internal comment".  Why not leave well enough along by leaving the default as it has always been to "Reply to customer"?  AND those small minority of teams that want default of internal comment can then toggle it if they require. 

I honestly have NO idea why anyone thought it was a good idea to change this default behaviour after 10 years of JSD/JSM being rolled out.  This is a SERVICE project which means servicing our customers which means "reply to customer" should be the default.

This is so typical of Atlassian.  Break something, then back peddle and put in a whole lot of effort and uproar to work around a very bad decision.  How about a bit of surveying among the Community champions ahead of time who really know their stuff before heading into these unpopular decisions.

Happy to discuss further and my community champions would be even more enthusiastic to discuss.

Susan

[Rick Westbrock]

Thanks for the EAP link and the update on the JAC to add a configurable setting for the transition comment type Jehan, much appreciated.

[Jehan Gonsalkorale]

Thanks @Rick Westbrock , always a pleasure! 

And I understand where you're coming from @Susan Hauth _Jira Queen_. The team spoke to a combination of partners and customers and received feedback that this was a preferred default, which led to the decision to push this change out. The reasoning from these customers and partners was that they didn't want "Reply to customer" to be the default to minimise the risk of accidentally sharing internal comments with your end customers. 

But this change impacted the lives of a lot of people and we should have been more careful and sought more feedback. 

So, I will be honest here: this was a mistake and we're doing our best to rectify it. 

I like your idea of getting feedback from Community champions before pushing out changes, particularly on product surfaces that impact so many people.  

I will be sharing this example internally to drive awareness of how seemingly small changes can have massive consequences for our customers and how we should engage with customers and partners in this forum and others before we push things out. 

Appreciate your feedback, it's definitely what we need to hear. 

Also, feel free to contact me at: jgonsalkorale@atlassian.com. It would be great to be in closer contact with you! 

Best regards,

Jehan