Activity
Mon
Wed
Fri
Sun
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

Atlassian Everything

281 members • Free

40 contributions to Atlassian Everything
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 like • 2d
I believe you can't opt out of metadata usage unless you're enterprise but you can opt out of in-app data usage. The documentation pages on this are poorly formatted but: https://support.atlassian.com/security-and-access-policies/docs/understand-data-contribution/ https://support.atlassian.com/security-and-access-policies/docs/what-types-of-data-does-my-organization-contribute/ Additional documentation with FAQs: https://www.atlassian.com/trust/ai/data-contribution
For those of you at Team 26...
What has been your favorite or most exciting announcement so far?
0
0
SOLVED: How to Copy Individual Public Comments from JSM Tix to Linked Jira Software Tix (Cloud)
Environment - Jira Cloud - Jira Service Management source project - Jira Software destination project What I'm Trying to Accomplish: I have an automation rule that fires when a JSM ticket transitions to a specific status. The rule creates a new linked Jira Software ticket in a separate project. When the new ticket is created, I need all public (non-internal) comments from the JSM source ticket copied to the newly created Jira Software ticket as individual comments - one comment on the destination ticket per original comment on the source ticket. Each copied comment should include the original author's name and the date it was originally posted. To be clear: a single consolidated comment containing all the original comments lumped together does not meet the requirement. Each comment must be posted as its own discrete comment on the destination ticket. The Question: What are my options for accomplishing this in Jira Cloud? Has anyone successfully implemented something like this? For disclosure: I've built a solution that *almost* works but not quite. I'm fully up for disclosing what it is, but I'd rather have suggestions that aren't tainted by me leading the witness. A solution that uses only native Jira functionality is preferred, but I do have Scriptrunner for Cloud in my instance, so it is on the table as an option.
1 like • 4d
Hi @Kent Guthrie, are you looking to: a) continue syncing the comments after the JSM issue reaches your specific status OR b) is it a "snapshot in time" in that you're copying all comments over when that transition happens and then from that point, the issues have their own lifecycles? If you want to continue syncing, are you intending to only sync public comments from JSM -> Jira Software or some form of bi-directional syncing? I think you can mostly accomplish this through Automation but the devil is in the details :)
Last Chance to Sign Up for Build IT Together: Anaheim
Hello, We have to turn in our final numbers to the venue for food and this is the last chance to secure your tickets for BIT: Anaheim. What you need to know: Hands-On Training Day: This is a full day (breakfast, lunch, Dinner, #AMA with Council of Jira Admins). You pick a track from the available 4 tracks. You bring your laptop and follow along as you actually build something. Get 20% as an Atlassian Everything Community Member with code: BITANAHEIMTRAINING20 Conference Day: This is happening right before Team 26. We'll have 12 sessions where you'll learn different ways to use the Atlassian Tools. We have some awesome sessions with even more awesome speakers. We'll feed you breakfast and lunch and then we'll all go to Team 26 which is just a few steps away. Get 50% off as an Atlassian Everything Community Member with code: TJL50. Bonus: If you'd like to get into the Conference day for free, then ping one of our sponsors or speakers. You can find the full list (along with with all the other information you want on our website: https://buildittogether.events/). They have special 100% off codes for the Conference day ONLY. See you all in a couple weeks!
1 like • 8d
@Denise Ellis in the same boat. Can't make it this year, sad that I'm missing out on what looks to be a great event!
Atlassian SSO - need the details and gotchas
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?
1 like • 11d
I haven't setup Atlassian Guard with Okta (all my clients are on Entra) but the way it typically works is for any user to be synced from the identity provider, they have to be a managed account by your organization which means their domain has to be claimed by your organization. That isn't to say you can't have other users in the organization but they would be treated as external users and wouldn't follow the identity provider's SSO policy.
1-10 of 40
Chris Rogers
3
1point to level up
@chris-rogers-3182
Atlassian Certified Administration Expert and overall Atlassian enthusiast

Active 17h ago
Joined Nov 5, 2025
Edmonton, Alberta, Canada
Powered by