Assets for Jira Service Management Cloud is getting bigger, faster, better - join the EAP!

[#1]

Hello Atlassian Community,

Jira Service Management is becoming a more robust and mature IT and Enterprise Service Management solution for Enterprises. Since the acquisition and integration of Mindville, we have been working hard to deeply integrate Assets into the Atlassian ecosystem with initiatives such as:

• A completely overhauled user experience.

• Integration of our API’s with Forge and Connect.

• Integration with Atlassian Analytics.

• Embedding Assets directly into Confluence pages via our new Assets table.

During this time we have also made major performance improvements to Assets Query Language (AQL) and Assets experiences in general. As a result of this we will be raising the limit on the number of Assets objects from 1 million to 3 million in the near future. Despite all this, the engine under the hood of Assets has remained fundamentally the same during this time. That is about to change!

A massive investment has been underway to re-architect Assets in Jira Service Management (Cloud) behind the scenes in order to make sure it can scale faster and more effectively with our largest Enterprise customers. We’ve set ourselves some ambitious goals which will bring big improvements for all of our customers across multiple dimensions.

Scale

While we are excited to bring you support for 3 million objects, we aim to allow much greater scale:

• Support for many more millions of objects.

• Substantially larger imports.

• Bulk actions over greater numbers of objects.

Reliability

Increased reliability of Assets to align with the Atlassian cloud uptime SLA.

Performance

Significant performance improvements across the board including:

• Assets Query Language (AQL).

• Imports

• API rate limits

Get involved!

The EAP will be starting soon and we are accepting signups for the waitlist here. We are looking for customers who are interested in trialing the new technology we have developed to power Assets and are willing to provide us feedback. You may be a good fit if:

• You actively use Assets (including on a sandbox site).

• You have performance, reliability or scalability needs that exceed what Assets is currently providing and want to provide input as we make improvements in this areas.

• Are open to being involved in Beta/EAP programs and providing feedback.

Initially our EAP may not support every single feature of Assets. Due to this we’ll be selecting customers who are users of the subset of features that will be initially available and including more customers as these features are added. The signup form has more information.

We can’t wait to start the journey of getting this into your hands!

Regards,

Justin King
Senior Product Manager, Jira Service Management

[Ashok Shembde]

Thank you for the update, @Justin King

It’s exciting to hear about the major improvements coming to Jira Service Management Assets, particularly the increased scale and performance. Looking forward to seeing how the re-architecture enhances reliability and usability for enterprises.

I'll keep an eye on the EAP and would love to contribute feedback when possible.

[Jimi Wikman]

Finally, some good news for Assets.

I just wished that this had come out BEFORE the announcement of the price changes, which I think killed Assets: https://jimiwikman.se/blogs/entry/11-did-atlassian-just-kill-assets/

For someone that have worked with PIM systems for E-commerce sites, I am still puzzled as to why there even is a limit to begin with. A modern platform should have no problem scaling near infinitely, and I don't know what could limit this for assets, to be honest.

Negativity aside, I am very glad that Assets are getting some love finally because I absolutely love Assets and I use it every day. There are many, many things that can be done to make Assets a must-have product and I hope that the refactoring is the cause for all the reduction of functionality and once the new architecture is in place we will see those limitations go away again.

I just hope it is not too late because most customers, me including, are looking for other solutions due to the degradation of service and the insane new payment model.

[Dave Mathijs]

Don't forget to mention the flip side of the coin: Consumption-Based Pricing for Assets

[Kelley R]

This is great news!

[Fabrizio Galletti (Euris)]

Great news, does this open up a possibility to manage import through cloud migration assistant from DC?

[Mat Cantarella]

This is fantastic news, will this include the ability for agents to create custom views and set them as a default? 

[Justin King]

Hi @Fabrizio Galletti (Euris)

Tooling to support migration from DC is seperate to this however I can tell this is something our teams are working on along with Backup and Restore, Cloud to Cloud migration, and copying data to Sandbox sites. Stay tuned for announcements regarding those. 

Hi @Mat Cantarella 

As part of this you can expect to see very minimal feature additions or UX changes. We are focused on performance, reliability and scale. However I can tell you the ability to create, save and share custom filters on Assets is something we are intending to provide in future so stay tuned. 

[Gabriel Points]

Hey @Jimi Wikman: It sounds like you're plugged into  this Cunsumption-Based Pricing for Assets... Do you know if child objects count towards the 50K limit? For example, I have an Asset object that has 3 child objects. My parent object count is ~ 1k. But then I have children objects nested in the parent object that add up to ~ 3K.

Would my count be just the parent object count of ~ 1k or the sum of parent + children (~4K)

[Justin King]

Hi @gab. In this case your count would be ~4k. On the Assets landing page you will see your total count displayed (screenshot attached) as well as a link to a more detailed usage dashboard.

[Birger Robrecht _avono AG_]

Is there any chance that disabled features (e. g. search in paragraph fields) will return with the improved capabilities or is this feature gone forever?

[Justin King]

Hi @Birger Robrecht _avono AG_

We always assessing and re-assessing the changes we make in order to improve Assets. At present we believe this tradeoff regarding search over large text areas is a good one way to help us hit our performance, scale and reliability goals with minimal impact to customers. However if you disagree I'd love to hear more about your use case for it!

[Birger Robrecht _avono AG_]

Hi @Justin King ,

Sure, I'll try to explain our customer's use case. We are using a two-level service structure: Business and Technical Services. We have a total of approx. 20k services. To ease selecting the correct business and technical service, the respective service owner maintains a list of keywords (e.g. Outlook for the Mail service). Depending on the service, the list of keywords can easily extend 255 characters, that's why we decided to use the paragraph field. As you can imagine, the search for keywords must be working.

The assets are synchronized from an external system. If the search in paragraph fields won't return, we have to restructure the assets and the interface and we will start using up to 4 text fields to store the keywords. As this takes time, I am investigating the options we have.

I am happy to share more details on this use case, just let me know.

Best regards, Birger.

[Marcela Junyent]

Subject: Inquiry on Asset Management Reporting Capabilities

Hi,

We are currently using assets in our JSM to track our incident categorizations (CTI) and are in the process of designing a full IT asset management system.

However, we are facing performance limitations, particularly regarding reporting capabilities across different schemes and analysis of historical data. Some of our reporting requirements seem to be overlooked in the current asset structure, which could be a significant drawback for us as we seek an effective enterprise solution.

We would like to know if there are any plans to improve these aspects and how we can provide our feedback.

Thank you.

Regards, Marcela

[Harrison Ponce]

This is exciting!