Have you ever worked with multiple projects and multiple emails ? We have several projects, and as we're optimising. I'd want to set up one project and associate distribution list to request. Can't find any solid info on this (as these emails are without credentials). For other projects I want to associate a better email to each project. Ie. Let's say we have one space for new business, and I'd want new_business email (this time either shared or an email with credentials) to link, as to get incoming tickets straight from the emails. I believe this is handled by Incoming Mail , under Jira admin settings, and then to be adjusted in space settings, notification email. Am I correct? If there's a video tutorial, feel free to share. (That's the last piece of the puzzle before completion of a massive optimisation of Jira and I can move onto other priorities. Would appreciate any tips, guides or instructions as to faster implement this.)

I think I saw something recently that indicated Atlassian is planning on forcing their clients to allow them to use their operational (re. proprietary) data for their internal AI learning. This is a no go for my CISO. Hard stop. Opting out seems to be limited to only Enterprise level customers? Is this correct? Am I imagining horrors that will never materialize?

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.

Tasked with moving our Atlassian Cloud tenant under Okta SSO. I understand there's a Guard piece we need, but I also think there's a limit on all users have to be managed users, which means all domains of users have to be included. And other stuff. Anyone done this? Where are the hidden gotchas?

Has anyone else heard anything about the possibility of Anthropic purchasing Atlassian? I saw this in an AI newsletter last week but short on details. What impact do we think this would have on Atlassian as a whole? Is this a move toward better AI tooling inside Atlassian?