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

Owned by Josh

Atlassian Everything

62 members β€’ $6/month

An exclusive community for Atlassian users to learn, share, and build smarter solutions that make work simple.

Memberships

APETECH

70 members β€’ Free

Community Accelerator

1k members β€’ Free

Skoolers

181.5k members β€’ Free

20 contributions to Atlassian Everything
Restricting KB content per customer in a shared JSM project
Hi all, I’m looking for some guidance on a challenge with JSM and Confluence as KB. We have a standardised JSM project used by most of our customers. One large customer was previously on a separate, customised support setup, and we’re now migrating them into the general service desk. They have product specific documentation that shouldn’t be visible to our other customers. Sensitive and irrelevant, potentially confusing to other customers. Atlassian has documentation suggesting to invite customers as Atlassian accounts to allow assigning them to groups and restricting content that way. However, when testing this, we found that any user with an Atlassian account, even with just the customer role and no confluence license, can navigate directly to our confluence and view KB articles of any service project, even the ones they do not have access to ad a customer. This would potentially expose internal teams KB’s such as ICT, legal, HR, … which is obviously not acceptable. Am I missing another way we can achieve this? How do you handle customer specific documentation without exposing other Confluence spaces? My personal gut-feeling keeps telling me they need a dedicated JSM project for this, but management has made the customer promises and has been working on this for months before it reached my desk and dont seem to want to backtrack now. Any insights or experiences with this subject would be greatly appreciated! Cheers, Thijs
0 likes β€’ 3h
hey @Thijs Van Baelen I have been looking into this all morning. From everything I can find, the only way to restrict permissions for specific Confluence pages is for the users to have a Confluence license. In this case, since they are customer... That is not an option. Unfortunately I don't see how this could be possible without having separate JSM spaces. πŸ™
Jira Automation - Surely there's an easier way?
Hey community! Sorry - long-ish post incoming I'm currently attempting what should be an easy automation but is really stumping me. I have set up a rule that when bugs in a particular space are resolved, that a slack notification occurs to let out stakeholders know that a bug has been resolved. Where I'm struggling is, that we want to "@" tag them in slack which should be easy right? GPT mentions that I could use a lookup table (I've got over 60 slack IDs to add) but our Jira (premium cloud upgraded version) doesn't offer Lookup tables as an option ?! πŸ₯². So instead, it recommends we use a create variable option "Reported by: <@{{var.slackMap.[issue.reporter.displayName]}}>" I've done that in the following format: Trigger: Issue transitioned β†’ Done ↓ Condition: Issue type = Bug ↓ Condition: Project = [space] ↓ Action: Create variable (slackMap) ↓ Action: Send Slack message I tested this with just one user/slack ID and it worked perfectly! However, when I added the full list of team members, it populated with this notification in slack: "DO-1234 has been resolved in the Customer Support project. Reported by: <@> View issue" so it's removed the "@" tag that was there when I tried with one example. GPT then said that Jira doesn't support <@{{var.slackMap.[issue.reporter.displayName]}}> (Sigh) My last option is the If/Else path, but not doing that for over 70 team members and it will be impossible to maintain! Any sanity checks/advice would be very much appreciated
0 likes β€’ 2d
@Orla Mears I went down quite the rabbit hole.... I think this is the best solution I found: https://community.atlassian.com/forums/Automation-articles/Send-a-Slack-message-with-an-mention-using-Web-Request/ba-p/2752942 Doing a lookup will probably be the simplest option. Otherwise if/else would be the way to go. Or maybe an asset database? πŸ€” The webhook is definitely going to be the best option since it will never need to be updated.
What topics are you interested in?
This will guide the next courses, live webinars, and more!
Poll
19 members have voted
0 likes β€’ 3d
@Corey Glaude I was tempted πŸ˜… I figured it can be bundled with the Methodologies option.
EasyBI
Hi guys, how are you? Is there any content that I can learn more about EasyBI? Thx!
1 like β€’ 4d
There is also a training series in their documentation: https://docs.eazybi.com/eazybi/learn-more/training-videos
How to speed up Confluence adoption with AI-first approach?
Breaking the ice by throwing a current challenge into the community. I am currently doing a Confluence rollout for a small real estate company. 4 people, planning to grow in the next year to approx. 15 people. Problem: The founder has very little time and the new sales employee is a complete newbie to anything tool related. Collaboration happens via email, phone and word documents. There is understanding, that a lots has to change. The biggest blocker currently is time, not willingness. I am now thinking about effective and non-traditional ways to speed up the process from 0 to 1. I helped the founder set up a claude project so he can record himself and collect his knowledge there, which helped already a lot. But I don't want to stop there and think of more ways on how do drive an ai-first approach. Any ideas? Maybe on how to include Rovo?
2 likes β€’ 28d
@Marina Dittrich By far the most effective approach we use, is to run requirements gathering meetings. It's more time consuming... but if you can get a 1 hour block per week, that would probably be the most effective way to collect information. Loom is also great. You can have the founder just hit record and talk through whatever is happening on screen. This gives you the full process without taking up any of the founders time.
0 likes β€’ 5d
@Marina Dittrich This is an awesome use case! I'll have to try and replicate it.
1-10 of 20
Josh Golosinskiy
4
79points to level up
@josh-golosinskiy-9101
CEO and Founder of GRYD.IO

Active 26m ago
Joined Oct 27, 2025
Powered by