I'm a Product Manager at Atlassian, responsible for the new people directory on Atlassian Cloud. Its part of our integrated profile transition, allowing you to see users profiles across both Jira and Confluence in one directory. It will replace Confluence's people directory soon.
You can get to it today by going to yoursite.atlassian.net/people.
We are about to start featuring the directory more prominently over the coming weeks and I was looking for some feedback on a couple of points. Visibility of other people can be a touchy subject, and we want to start transitioning from a configurable people-visibility approach to a "smart-default" approach.
Today in Jira, administrators can grant the "view users and groups" global permission to groups on their site. This controls who can see other users in things like user pickers and mentions. By default, this permission is granted to the license group, but many customers customise this setting.
We want stories to help us understand why and how administrators are applying this setting at Jira.
Today in Confluence, it is not possible to restrict visibility of other users, as all licensed users appear in the directory, mentions, and user pickers. There's a customer suggestion to allow similar configurations for Confluence.
We want stories to help us understand why and how administrators are applying this setting at Confluence.
We think user to user visibility can be improved. We use visibility rules in the new people directory that we believe are better suited to collaboration. We want your feedback on whether we've got it right or wrong. Most importantly, we want to understand why...
Who can I see, and who can see me in the new people directory?
When viewing directory, you will see a blend of two sets of users:
Anyone you can see based on these rules can see you too.
We plan to allow Administrators to see all users on a site, as an exception to these rules. This would mean an admin could possibly see a user that cannot see them. This won't be in place on day 1, however.
We chose this rule set after careful consideration, as it creates a set of natural soft boundaries of collaboration within a cloud site. Businesses with a simple setup of collaboration within the company will be able to see all other people from the company, businesses with a more complex setup including vendors, clients, or contractors won’t unintentionally reveal all other users on the site.
This rule set only applies within people directory at this stage. The Jira configurations are unaffected.
People directory will replace Confluences people directory in the near future, and be available for all licensed Jira and Confluence users on a site.
Again, you can get to it today by going to yoursite.atlassian.net/people.
I'd love to hear why you think these rules are great or terrible, and whether they will help you or hinder you getting more s#!t done.
Let’s face it: most of us have too many meetings on our calendars. And few things are a bigger waste of time than recurring meetings that no longer provide any value to attendees (or the busines...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs