Rusty (Matt) Atlassian Team

Hey Mick, When you're actually viewing the filter results, you should see a "Details" link up next to the name of the filter. Under this, you can see who owns it, and alter who has permission to it. The permissions setup is fairly flexible, so hopefully you'll be able to get the right people access. Let me know if that…

Hey Nickey - I'm sorry for such a horribly late reply! Yes, you've got it right. The team is currently looking at putting email notifications in place so that people you invite will get emailed, but for now, if the person visits the team profile, they can accept, then they will become part of the invite. Note that this…

Hey Merve, Thanks for providing your thoughts. You've guessed right about the fact that Teams will share a lot of characteristics of groups. You're right that end-users will be able to create and modify them themselves too! In fact, only team members can modify teams - so it's a hands-off experience for Admins. We are in…

Hi @Gabriel Radic, @Normand_Carbonneau, @Dave Winter - I want to be clear here that the visibility scope we are discussing is user profiles. Nothing I have proposed is about the permission of content on a site (e.g. project, space, page, issue, etc). Rather it's the ability for someone to see another user's profile.…

Hi @Gabriel Radic - just to be clear, your statement indicates that * john@ourcompany.co should not be able to know that jim@ourcompany.co exists, and vice versa. * emma@clientshop.co should not be able to know that emil@clientshop.co exists, and vice versa. * danna@designersinc.co should not be able to know that…

Hi @Björn Wennerström - did you have a read of the rules described for the new people directory? This is exactly what we're trying to achieve, with zero setup / maintenance required. When viewing directory, you will see a blend of two sets of users: * All other users on the site who’s email domain matches yours. This…

Thanks for this feedback. Can I ask you to get in touch for a face to face interview? I'm not sure I am clear on your purpose behind this setup. And I'm unclear why / whether the email domain rules described for the directory would or wouldn't be in breach of your current setup. I think a conversation would go a long way.…

Thanks for the feedback @Normand_Carbonneau, @Jim Lynch, @Dalectric - I think Delectric has hit the nail on the head here. Mentions within the context of a piece of content can be scoped to something like "who has access to this content". That becomes a very granular rule, and potentially confusing that I can see someone…

Thanks for the feedback Arjan, @Dave Winter, We would like to avoid a total blackout of features for users. Customers are people too, and deserve an experience that's first rate. A "blackout" approach is a last resort, and while we might explore depending on the insights I get out of the feedback here, we'd really like to…

Hi @Roel Croonenberghs & @Gabriel Radic, If I'm understanding correctly, what you're describing sounds like it is fairly close to the rules we have in place. If we apply the assumption of email domain creating an automatic grouping / permission. But you've suggested that doesn't hold up - can you help me understand better?…

Hey Andy - is there a ticket you can point me to for this on jira.atlassian.com? I can double check whether it's been resolved with the new directory. 

Thanks for the feedback so far everybody. I'll take some time to consider and potentially reply to each comment here, but just wanted to let you know I've received and started to think through the comments. Keep them coming!

Hey Benjamin, I'm the Product Manager at Atlassian looking after this consolidation. We definitely want to have things pointing to a single proflie eventually, but there are quite a few ducks to get in a row for that to happen. We will need to chip away at it. Let me know if you want more info, or if you want to be…