Justin King Atlassian Team

Hi @Franziska Kress Sorry about this. The team is looking into your issue now. I see that they have requested some extra info from you on the ticket you logged. We'll get it sorted!

Hi @Joseph Chung Yin While the events captured may differ a little from Assets in cloud, Assets in DC definitely already has good coverage in its audit log. 

Hi @Dave Meredith This is a part of that. There are some additional things we need to do to increase that limit and ensure we maintain acceptable performance and reliability. We are working toward these as well. 

Hi @Hayley Skelton If you like, please reach out to me at jking@atlassian.com and pass me your site URL. I'll double check for you that no actions are required. 

Hi @Josh I have checked and your site no longer looks to be breaching any limits. You may have been breaching one of them at the time when we sent the original email and since then your data has changed. Nothing for you to do here!

Hi Sonya, Sue and Hayley, What may have happened here is that between the time that we sent our first notification and the most recent one, you switched from not breaching any limits to breaching some. Hopefully if this is what has happened the changes you need to make are very minimal? I apologise for this coming as a…

Hi @Sonya Petkunas Its possible you were one of the few customers who only began breaching one of these limits between the original mail out and yesterdays mail out. Sorry for the surprise. The email will contain links to downloadable reports which will tell you exactly where any changes need to be made. 

Hi @Gunjan Ahuja. I'm sorry but we don't have the ability to re-execute any automation rules that will have written to Assets during the maintenance period. Hey @Chisato Saito. Unfortunately until a site aligns with the limits we have introduced such as max 120 attributes per object type we are unable to ship improvements…

Thanks for the feedback @Milad Sayad! I'll pass that on to the team.

Hi folks, @Mathew Ledermana quick update on the bundled release track issue you have raised. We looked into this and it seems the Assets app rollout was not included in the bundled release track. According to the definition here https://support.atlassian.com/organization-administration/docs/what-are-release-tracks/ it fits…

Hi folks! To clarify a few things: * We don't have the downloadable report available yet but its being worked on right now. Stay tuned. * The report will only be relevant to you if there is something preventing us migrating your site. If you have received no prior email comms from us regarding this matter then assume there…

Hi @Mathew Lederman I'll look into how the change could have been rolled out on your site so quickly given you are on the bundled release track. As for the release notes. You can view them here as well as in-product by * Selecting Help (?) from the top navigation bar. * Selecting Find out what's changed in Jira. You can…

@Rick Westbrock an update on respecting Jira's custom nav colours, logo and favicon. We are beginning work on this right now. This is not a large piece of work so we expect to have it in your hands before long. 

@Mathew Lederman as with all new features this is being rolled out progressively to customers on the continuous release track. Those on the bundled release track will receive it on a longer timeline. It is included in our standard release notes.

Hi @Rune Rasmussen and @Dirk Ronsmans This change does not have any impact on the current pricing and packaging of Assets. It's still only available with the purchase of JSM Premium and the existing consumption based pricing still applies. Thanks for your feedback though. Thanks for the feedback @Rick Westbrock We do…

Hi @ankur_patel Could you elaborate on your use case for UC on a TextArea? Thanks!

Hey @Meetbhai Yasheshkumar Dave and @Sean Kraft We are preparing to begin rollout of the new Assets backend at the moment. It will take a while to do this for all customers but for sites still breaching limits those we will move those to later in the rollout process to allow time for customers to adjust their data and if…

Hi @Daniel Vest That change has no effect anywhere except for usage in import mapping so your automation rules will be fine!

Hey folks, An update as promised. To help make this as painless as it can be, we are preparing a downloadable report that will outline exactly where changes need to be made in your sites Assets data to comply with the new limits. We expect to have this available by mid-April and will share details on how to access it once…

Hey folks, An update as promised. To help make this as painless as it can be, we are preparing a downloadable report that will outline exactly where changes need to be made in your sites Assets data. We expect to have this available by mid-April and will share details on how to access it once it’s ready. If your struggling…

Hi everyone. I apologise if this has caught you off-guard. I agree we should have sent the reminder email sooner. On the issue if locating your attributes that currently have unique constraints. Thanks for the feedback, I can see how in some cases this could be challenging. We are evaluating how we can help with this and…

Hi everyone. The reason for this new limit of 2 unique constraints per object type is that the addition of large numbers of unique constraints is a contributor to performance problems. This is not something specific to Assets, but to all database systems. We are aiming to ensure we can offer high performance while also…

Hello all! A little late updating this post but I just wanted to let you know that support for 3 million objects in Assets rolled out to all customers as of last October. All the best! Justin

Thanks for that Dirk! In this case I don't believe you will be effected. In your import mapping for the Mobile Phone object type the configuration would be: * Data source field: owner (assuming this is the name of the column in your import CSV) * Destination attribute: Owner * AQL: EmployeeID = ${owner} Remember the AQL…

Hi @Dirk Ronsmans Would you mind helping my understand your example in a little more detail? What I'm not quite following is why the SerialNumber that is the primary identifier in the data is not an attribute on the object type you are importing into. Thanks!

Hi Dave and Kevin, I understand it might seem that way. The reason is we are heavily re-working the underlying platform that drives Assets. It will allow us to offer greater reliability, much larger scale and better performance. However the shift to a different architecture means that a small subset of features need to be…

Hi @Jordi Garcia I'm sorry you were disrupted by this. The reason we are removing this is that the underlying implementation of AQL is changing as part of https://community.atlassian.com/t5/Jira-Service-Management-articles/Assets-for-Jira-Service-Management-Cloud-is-getting-bigger/ba-p/2838687. Maintaining some…

Hi @Jonathan Boulgier I'm sorry to hear you were disrupted. We did announce that this change was coming with approximately 6 months notice on Atlassian Community, Atlassian Developer Community, and in the Atlassian changelog as is our standard practice. It sounds like in this case additional messaging may be been useful to…

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…

Thanks for the feedback @Tim Eddelbüttel You raise an excellent point. I'm discussing this with our team to see if we can alter how we go about this. Stay tuned.