Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
8 contributions to Atlassian Everything
Concerning Marketing Email from Atlassian
We have now received two emails from [email protected] that are focused on this: Shaun, stay on top of your work with these prompts. What follows is a list of three AI prompts that reference data and functionality unique to our business, our systems, our own AI tooling. What deeply concerns me is Atlassian was never given permission to use our tenant data for ANYTHING. I explicitly rejected their request to share our tenant data with others when they put that out a few months back. I checked again today and that setting has not changed. Of course the deeper concern is that I have no one at Atlassian that I can even reach out to for this. Does anyone else get these messages and do they also contain data exclusive to your tenant?
May 18 • 
JSM
JSM Customer Portal Customization
Does anyone have a solid recommendation for a marketplace app or tool to help me fully customize the JSM customer portal look and feel. I've managed to do a little with the built in tools, but I'm being asked to get the thing to look like our full corporate style. Not sure if there's anything out there, but thought I'd ask.
Getting granular with Issue/Work Item history
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.
0 likes • May 18
We opted (for now) for a marketplace app. But we will likely just create a Claude thingy to pull the data we need.
Apr 28 • 
Jira
Distribution list email link to Request
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.)
0 likes • May 7
If you are talking about inbound emails turning into a JSM request, that's the EMAIL channel option in your JSM space. I believe (could be wrong) but you can setup up to 10 email addresses to come into your JSM space, and link them to a request type that gets created. Point your favorite AI chatbot at that and it should walk you through how to set it up. What I've done to simply work ingestion this way (from email) is to use mail flow rules (inside my M365 Exchange Admin Center) to capture emails sent to multiple different shared email boxes (inbound email) then embed a code in the email subject line that tells me what mailbox the email arrives in, then redirect to a single "hidden" email box from which I ingest the email into my JSM space. Multiple Email Address → hidden email hub address → JSM space → generic request type for initial ingestion → automation rule to read the code (now in the work item summary) and then reassign to a correct request type. Took time to setup but now it scales nicely if I need a new email address with a new request type, I set a mail flow rule and add another branch to an automation flow and I'm good to go.
0 likes • May 8
Ingest in JSM space, deep clone immediately to a Jira space. Deep Clone is an amazing app, not expensive, and just works. I use it this way all the time.
Protecting my operational data from Atlassian (and whoever they end up sharing it with)
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?
1-8 of 8
Shaun McGuire
2
7 points to level up
@shaun-mcguire-6514
Atlassian org admin, learning as I go. Five years in, I know enough to be dangerous.

Active 2d ago
Joined Mar 4, 2026
Powered by