Optimize team member ux

[kerwin612]

Try to solve #22054

[wxiaoguang]

TBH if you have "all teams" here, then the "pager" doesn't make sense any more.

[wxiaoguang]

Isn't the "all teams" link already in the navbar?

[kerwin612]

My original intention was to provide a more eye-catching entry on the secondary page.

[wxiaoguang]

Why members list page should show "add new team"? I guess it should show "add new member" instead?

[kerwin612]

Just like above, there is no mistake. It is indeed about adding a new team. My original intention is to provide a more eye-catching and convenient operation entry on the secondary page.

[wxiaoguang]

Before making more changes, I think there could be a better design, instead of adding the modal.

The root problem is that "it is not clear about how to add a team member". To make it clear, we can just:

1. Remove the "View" and "Join" button from the team header on the teams list page, and add a "Add member" button.
2. Add a prompt message on the "members" page: To add members to this org, please go to Teams page, add the user to a team.

[kerwin612]

Before making more changes, I think there could be a better design, instead of adding the modal.

OK, I'll implement a version according to this train of thought and see the effect.

[jbrubake]

Before making more changes, I think there could be a better design, instead of adding the modal.

The root problem is that "it is not clear about how to add a team member". To make it clear, we can just:

1. Remove the "View" and "Join" button from the team header on the teams list page, and add a "Add member" button.

2. Add a prompt message on the "members" page: To add members to this org, please go to Teams page, add the user to a team.

TBH I don't understand why you wouldn't want the Add Team Member button on the Team Member page. That's where I go every single time I want to add a Team Member because that's why I assume such a button would be

Unless I'm misunderstanding your comment

[wxiaoguang]

TBH I don't understand why you wouldn't want the Add Team Member button on the Team Member page. That's where I go every single time I want to add a Team Member because that's why I assume such a button would be

Unless I'm misunderstanding your comment

"2" is exactly the same as adding a Add Team Member button on the Team Member page, while "2" is more consistent and maintainable. I don't see any fundamental difference.

[jbrubake]

TBH I don't understand why you wouldn't want the Add Team Member button on the Team Member page. That's where I go every single time I want to add a Team Member because that's why I assume such a button would be
Unless I'm misunderstanding your comment

"2" is exactly the same as adding a Add Team Member button on the Team Member page, while "2" is more consistent and maintainable. I don't see any fundamental difference.

Putting the button on the Team List page and adding a note on the Team member List page that directs you there is definitely not the same thing (apologies if I'm misunderstanding your proposal)

Logically, I go to the Team Member List page to add someone (I do this every time because I can never remember how to actually do it). With your change I'd still do that and then have to go somewhere else to do the actual adding

That's bad interface design--functionality should be intuitive and not require the user who did the intuitive thing to be redirected to a non-intuitive location

[wxiaoguang]

Putting the button on the Team List page and adding a note on the Team member List page that directs you there is definitely not the same thing (apologies if I'm misunderstanding your proposal)

I don't understand why they are different.

• Put a button:
  • End user clicks the button
  • Navigate to the "add team member" UI or modal dialog
  • Choose a team to add a member
• Put a prompt message with link (or even button-like link):
  • End user clicks the link
  • Navigate to the "team list" page
  • Choose a team to add a member or add a new team

Actually "Put a button" does worse in this case: what if there is no "team"?