Any ideas when Assets will be fully functional?

[Mathew Lederman]

Does anybody have any idea when JSM Assets will be a functional tool in the Cloud environment? There are so many process-breaking bugs that I'm hesitant to encourage team members to use it.

• Non-Jira Admins can't export more than 14k rows
• AQL Queries with more than 20 objects can't be exported
• JQL references Assets by their ID rather than friendly name making it nearly impossible to share a filter
• Assets can be used to determine approvals in JSM Workflows on DC. Not so in Cloud
• Assets API is so significantly rate limited that we have to stop some users from performing basic queries because it throttles the entire instance
• Any Automation rule that references an Assets custom field takes 70+ seconds minimum causing issues for rules that run often in a single day. Again, this is due to issues with the Assets API
• Many plug-ins can't utilize the Assets API because it's not fully flushed out, not well documented, and doesn't offer sufficient capabilities

The list goes on, but I would love to hear any options and/or alternatives teams are using to work around these issues.

[Rodney Estrada]

It would be great to also have a native automatic bidirectional syncing feature for Jamf and Intune when an attribute is changed.

Jamf ---> Assets

Jamf <--- Assets

Thank you,

[Mathew Lederman]

I'd settle for native Jamf > Assets and Intune > Assets. Sorta like what's available in Datacenter today. Unfortunately JSM in Datacenter is light-years ahead of Cloud