I've written an agent to help write scripts/speaking points for Jira Custom Onboarding. The intent is that it will read an onboarding template and can generate both the 500char summaries for onboarding, and the 5min video script. More info here: https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/From-Zero-to-Scalable-Building-a-Custom-Jira-Onboarding/ba-p/3212524

@Tei M. my former org had both BambooHR and then Hibob. We had Okta, so users were added via Okta Workflow into Jira, JSM, Confluence groups. Did not have users as Asset Objects, but i wouldn't be surprised if the process was the same.

@Orla Mears I've written a piece on this in Atlasssian Community. https://community.atlassian.com/forums/Jira-articles/Jira-Governance-Navigating-the-Space-Between-Autonomy-and/ba-p/3156269 Personally, I don't see how a new instance helps, unless absolutely every aspect of the instance is a mess, and everyone agrees to default screens and default 3-step workflows. It also depends on what type of mess you are in. Is it a duplicate custom fields, dead projects mess? Security groups / permissions mess? Workflow mess? Unused licenses / resources / apps mess? Not every unruly instance is the administrator's fault. For example: If you have an instance with abundance of workflows where engineering teams are using different workflows to do the same work, that's an issue with the xDLC to be resolved with an agile coach and Dev leadership.

This question inspired me to write an article: https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/The-Three-Pillars-of-Effective-Jira-Governance/ba-p/3199351

I learned by doing. For me this looked like getting an API key set up and then using postman to explore the API. I felt that cloud API was a bit limited compared to DC API, and I ended up writing python scripts. one thing i found useful with the API is the jql endpoint. This one allows you to select a group of records by providing a jql and then pulling them down via api. python is then used as transformation layer to stage the data or perform additional operations on it that API cannot do

For sure use-based pricing is coming on Rovo side. I think Plans will likely get built up into a stand-alone project management product that's closer to monday.com or Asana. Not yet sure how Atlassian will leverage that recent browser purchase.

@Josh Golosinskiy That's a reasonable forecast and it makes sense. At bare-bones product & engineering level which is the starting point for many tech start-ups, there are simpler options like GitLab. Sure, it doesn't have all the bells, whistles and a thriving app marketplace, but at that org maturity level most teams just want to manage sprints and write code. Other early-stage businesses who don't write code can probably get away with simple task managers like Trello. Atlassian as a platform shines brightest when orgs mature into needing consistent, traceable, transparent workflows, and your whole org (or at least most departments) are looking for a way to run this in a unified ecosystem. Both project management and crm capabilities seem like a closer fit with the platform as it is today. Email/Messaging and Calendar (beyond what Confluence has) seem more as an outlier.