About Consumption-Based Pricing for Assets

[Chisato Saito]

Hi there,

Consumption-Based Pricing for Assets are just updated.

I have a Assets that stores more than 200,000, however it is expensive after this pricing rules offered.

What do you do after this offered...(especialy someone who use Assets stores more than 

one hundred thousand)

 Is there a work around? :(

[Ralf Scheller]

Hello, we also struggle with this new pricing. At the Moment we have about 240.000 Objects and we are at the beginning of our implementaion of JSM with IncidentManagement, ServiceManagement and want to expand to ESM. So we are working with IT-Assets as well as Non-IT-Assets.

We did many hours of implementation to build import-functions to get Assets from several other sources for usage in ESM.

Now we have to decide, if we look for alternatives, if we pay more than 100.000EUR per Year additional to the User-Licensing, if we reduce our Asset-Number (with lack of comfort) or what else we could do.

Not to forget - There is still NO Backup for Assets from Atlassian!! For being secure, we would have to pay another App for managing the Backup.

If anybody has a goog Idea - let me know.

[Chisato Saito]

Hi, we are concidering to use ticket to manage DB data instead of asset objects, these tickets are would be massive amount of tickets although.

[Dirk Ronsmans]

Unfortunately there doesn't seem to be a workaround (except maybe look towards other Asset management marketplace apps and move away from Assets).

Evaluating your data and cleaning up would be step 1.

Reaching out to whoever managed your licenses regarding discounts/volume discounts would be step 2

[Chisato Saito]

thank you for answering.

we need considering to the way of store information because we are solution partoner...

[Walter Urrejola]

I’m reaching out to express my deep concern about the recent changes to the Jira Assets usage quota, which are having a major impact on my operations. I currently manage 230,000 objects in Assets, and the new restriction of 50,000 leaves me in a very difficult position. It’s simply not feasible for me to pay $100,000 to maintain the current setup. These changes are directly disrupting my growth plans with Atlassian, which I have carefully built over time. The lack of flexibility in this transition, combined with the high costs, is pushing me to seriously consider moving away from Atlassian altogether. The constant uncertainty about future restrictions only adds to the difficulty of planning for the long term. I’m also very concerned about the short timeline for adapting to these changes. Could someone please clarify what the 12-month grace period actually means? It doesn’t seem like enough time to make this transition without causing significant disruption to my operations. I appreciate your attention and hope to receive a response that offers a viable solution, especially considering the trust and investment I’ve placed in Atlassian over the years.

[Trudy Claspill]

@Walter Urrejola 

Per information I have received as an employee of a partner, grace period information was being sent directly to the clients that are using JSM Cloud Enterprise already and exceed the 50k limit. Has your company received such information?

[Walter Urrejola]

Hi @Trudy Claspill , thank you for your response, we currently use JSM Cloud Premium and have not received that information.

[Xijie Yi]

We are having a similar issue as well. In your case, even with the discount, you will still be charged an extra $75,000 a year. :( We purchased the PREMIUM version because of the Asset Management feature, but now we will try to reduce the use of this feature.

[Chisato Saito]

We need to re-propose to our customer:(

thank you for answering, if you can find anything please let me know...