Skip to content

should projects require a team #101

@JohnRDOrazio

Description

@JohnRDOrazio

Seeing that the idea is going to be to allow more than one user to have access to a project, should we implement "teams" associated with "projects"? or would that unnecessarily bloat the logic of the application?

An example of this here: https://web-crunch.com/posts/lets-build-with-ruby-on-rails-project-management-app

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions