Skip to content

The logic behind the functions of team and organization should be clearer #34718

Open
@huifeideteji

Description

@huifeideteji

Feature Description

All the team list bind with organision rather than independent exist.When i created a repository belong an organization,all the team will appear in the co-worker list and i cant remove it.I think it's not beneficial for permission management.
For example,Joe have confilict with others,we dont want Joe participant in develop of repository A any more,but Joe sitll need to develop B and C repositories.All the repository belong with XXX orgnazision.Ideally,we can set another team in A, add everyone except Joe to it,and then delete the old team.Or just remove Joe from team of A, but keep him in teams of B and C.The current situation is team binded deeply to organisation,we can only choose to let Joe leave the team completely or let him continue to participate in the development of all repository.(Joe is fictional, but he cannot finely control the team is reality)

Screenshots

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    type/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions