We are developing a feature in which a user can send an email to other users within the same Jira instance. Our initial idea was to use a multi-select component in which you can select one or more users.
With the new privacy settings, some users will not allow us to see their email address. During the ecosystem design meetup you gave us some interesting examples on how to solve this. (unfortunately I can’t find the recording anywhere, so I’m not sure if we’re taking the same approach)
I believe it looked something like this, which allows you to see which user has opened up their email address to the Jira instance:
Since we are designing functionality that requires the email address of the user, I’m wondering what the best approach would be to alert the user at this moment. Using @bmorgan in the example above is not possible, since we don’t know this person’s email address.
I can come up with a number of approaches:
Only show users that have an email address available. This could be confusing when you’re looking for someone and kind find them. You have no way of knowing why this person is not in the list.
Disable the selection and show a message explaining why it’s disabled. This seems like the best approach since it explains what’s going on. If you know the email address of this user, you could enter the email address manually.
Show some kind of error message when you select a user that does not have an email address. Similar to the 2nd option, but less elegant.
My main question here is: How does Atlassian deal with this situation? The best solution is usually the one that users are familiar with.
This also answers your question “Do you need help designing an experience with partial user data?”. It would be very helpful to get an idea of how Atlassian is handling these use cases, so we can take it from there. If we all take different approaches, it will become frustrating for the end-user.