Hey everyone, Wanted to get people's thoughts on what they might have used from a reporting perspective to show performance (such as velocity) at org level without the use of paid gadgets? I've only thought of adding i-frames into confluence (but this is a poor offering to exec teams and the format is bad as it shows the entire page not just the velocity report. The AI savvy people in our teams are starting to use MCPs such as Claude, but the connection and effort required to get the correct prompts required is too much in my eyes (but I'm becoming old school in that regard) I'd like an out of the box solution instead of coding AI to get me various results. Any help appreciated, this won't be just a one and done requirement, I envisage that it'll be an ask for almost every other metric that we can get from Jira

Is Rovo worth the hype? Watch this week's Jira Hot Topic Discussion!

What's your preferred way of work? Especially for work or Atlassian Jira, when you inherit it all from prior colleagues. :) You like to set up everything anew and customize from there, or you rather organise, cleanup and optimise the inherited "mess"? :)

Hey everyone! As I was brushing my teeth this morning (which is usually the time I'm most reflective), I wondered how other orgs that you guys work in or have consulted with like to manage your workflows and schemes? I've worked in both a very disciplined and totally chaotic environments, and really see how essential it is to have consistency across teams. In the past, we have leveraged that by having a single scheme and workflow across multiple spaces (and with some minor exceptions for non tech teams kept a like for like mirror image of those items with some minor adjustments based on their individual team needs) But on the flip-side, if you need to put mandatory fields or validations on workflows to improve the discipline of some teams but not others, would you feel that having several duplicate schemes works best in these regards? Or do you just apply a one size fits all approach and stick with one single instance?

We are looking to keep optimizing our service project early this year and have a few add-ons in mind (which will some of our own support gaps, but also a few things JSM doesn't do out of the box). What are your top 3 must-have Jira add-ons and why?