Marketing folks have listed "Asset and configuration management" under the "Standard" tier for the Service Collection here: https://www.atlassian.com/collections/service/pricing What is weird is that they are allowing those who only had JSM standard to migrate early to the Service Collection (with same pricing) or be migrated automatically (sometime this Feb is what it told me). I accepted the Service Collection Standard move from just JSM standard for one of my sites to happen now. This was actually a few days ago. I ended up with "Customer Service Management" but with no access to "Assets" yet. After submitting a support request, they tell me: "...I understand you have a question regarding the 'Assets' Feature within your Service Collection. I know you’re excited to try out this new functionality, and apologize for the inconvenience this has caused. While our features and pricing page does state that Assets is included for Standard plans, please note that there have been some slight delays in getting the feature rolled out. At this time we are targeting an early-mid February release for the Assets feature for all Standard plans. I realize the discrepancy between the information and actual practice isn’t great, and appreciate your understanding. I will pass this feedback along to our team for review as well. There will be a Community Blog post when the feature does officially become available. Please let me know if you have further questions as this time." Also, expanding "Assets pricing" at the bottom of the page at the link above shows a clear contradiction in the first two paragraphs: "Asset and configuration management is included in Service Collection Premium and Enterprise plans. Included in these plans, Standard customers will be allowed to store 5,000 Assets objects for free, while Premium and Enterprise customers will be allowed to store 50,000 and 500,000 Assets objects for free respectively. Above this limit, objects will start at $0.02(USD)/object/month with volume discounts."

Has anyone seen this yet in JSM request form editor??? I couldn't find any information related to this.

I'm wondering if it's possible to produce a CSV file in-house and upload it somewhere in the cloud (ideally in Atlassian's cloud) for JSM to access? It would be a file with our JSM customer's email address, organization code, and department name so would need to be accessed for every ticket. Can this be done? I'm asking because we recently purchased the Shared Data for Jira Fields app and we're probably going to face firewall permissions issues with that app "touching" our Oracle systems or data warehouse directly for this data.

Just wondering if anyone has encountered any "gotchas" when making the transition?

I'm configuring a new company-managed space in JSM and using SLAs for the first time. The calendar feature is so handy for "counting down the clock", but I keep gravitating towards using just automations with business days because I'm having to write so many short automations to send reminder emails before SLA breaches and escalation emails after breaches. Am I looking at SLAs the wrong way?