I am currently engaged in consulting a german authority regarding the DC EoL. Besides the political aspect which I do not want to cover, there is the technical aspect. What I am curious about is what kind of strategic moves do you already see on the horizon? Like the following: - Asset likely will be untied from JSM - usage based pricing: Asset objects, Rovo conversations, AI usage - push towards collections - more than the usual 10-15% pricing increase when DC is sunsetted Maybe I missed some tendencies, which are already obvious?

For the simplest HR Onboarding, Offboarding and Change of Role within JSM. I've been researching this topic again recently and whilst I like some Atlassian updates, the material out and about makes you think this is very hard to make, including Jira and JSM having to sync,... (Multiple tickets, automations, etc.)

Hi everyone! I’m curious to hear your best practices when it comes to being data-driven in Jira. - What reports or dashboards do you rely on most — and why? - How do you use Jira data to support retrospectives and continuous improvement? - Any tips for improving data quality or avoiding misleading metrics? - What’s something you’ve seen work really well (or not work at all)? All perspectives are welcome! (Scrum, Kanban, hybrid) Best regards Simon

How do you make use of Versions? Does it differ between Jira and JSM? I am enhancing my habits to do a new version , for when I update a workflow, or add an automation rule, etc. (IE. Enhancements per project or space)

Anyone using components, in what way and/or use cases, best practices? I found this function and unsure how to feel about it. I rather have Space Owner being the Assignee, unless we work in teams and implement round robin or automations (for a junior role for onboarding, etc.)