We have a specific use case that is giving us fits. Here's the gist: - jira query with status transition and assignment history (assuming it's possible) of CRs - analyze with codex to create a report which would contain, at a minimum Backlog Metrics - Total "Active": the total number of CRs not in status "done", "rejected", or "in prod". - Untouched: the number of CRs which have no comments and no changes in status - Wait and Rejection Metrics (90 Day Rolling) - 90 Day Average Wait Time: the average amount of time a CR currently in status "development backlog" or beyond spent in "waiting for customer" status over the last 90 days - 90 Day Rolling Rejections: the total number of CRs moved to status "rejected" over the last 90 days - 90 Day Rejection Reasons: of those CRs rejected over the last 90 days, how many of each "Rejection Reason" occurred - Goals - Mean time to resolution (MTTR): across all CRs which are currently in status "development backlog" or "sprint backlog" or farther along in the workflow, what is the average amount of time they took to go from status "delivery backlog" to "done" In the past I looked a couple of marketplace apps but they didn't really fit our use case with specificity. So my big question is: can Rovo or a Rovo agent pull this data that I can then feed into Codex/Claude Code/Gemini for analysis. I'm thinking if we could just get the raw history of the work item the AI could do the rest.

Hi all, I've got a unicorn scenario and was wondering if anyone knows anything about potential of migration from Gov Cloud to Commercial Cloud. This scenario is apparently unlikely based the fact that organizations tend to move from looser to stricter compliance environments. Atlassian seems to reflect this by having various guides covering cloud to agov, dc to agov, agov to agov, but nothing in the opposite direction.

The 'c' to create a Jira issue shortcut. I personally hate how it can be triggered in the weirdest places, where I would almost never create an issue (like setting a field context with an issue type and a project that both have the letter c in them). I know keyboard shortcuts can be disabled per user, but it's only that particular shortcut that grinds my gears. What's your Jira/Confluence pet peeve?

Hi team, We're looking at running a full audit of our Jira instance and have been talking to a local solution provider. To be fully transparent, our instance is chaotic and there is (was) no governance whatsoever. Outside of duplicated fields, schemes etc, I wonder what should we be looking for from the consultant, I am probably too focused in on the Jira cloud instance but really need to get best value from this audit and then look at our broader Atlassian accounts. Thanks all!

Hi Atlassian Community, I’m don’t know if this is the right place to ask. Apologies in advance, happy for advice and guidance. I’ve spent several years working extensively with Atlassian Data Center environments across Jira and Confluence, covering upgrades, migrations, integrations, platform engineering, security governance, risk, controls, and operational support within complex enterprise environments. Recently, my role was made redundant as part of organisational changes, and I’m currently exploring new opportunities within the Atlassian ecosystem. One thing I’m actively trying to understand is how best to position and showcase deep Data Center experience in today’s increasingly cloud-focused market. A lot of organisations understandably prioritise Atlassian Cloud experience, but for those who have successfully navigated this transition, I’d genuinely value your perspective: - How are you positioning your Data Center expertise today? - Which aspects of DC experience resonate most with employers hiring for modern Atlassian roles? - What cloud capabilities should experienced DC engineers prioritise first? - Are organisations still valuing hybrid or transformation experience during cloud migration journeys? Would really appreciate guidance, industry perspective, or advice from others in the community who’ve gone through a similar transition. Also happy to connect with teams or professionals working in enterprise Atlassian transformation, governance, migration, or platform engineering spaces. Regards