Menu

#802 Add Feature: Teams/Organizations similar to Trello

Teams
open
nobody
2026-06-20
2017-02-08
Anonymous
No

Originally created by: xet7
Originally owned by: xet7

From @aegrey on December 18, 2016 1:53

Feature Description

Similar to Trello, an administrator would be able to create a Organization/Team/User. Any boards created under this team would be accessible to all members of the team. Very high level of changes would be:

Discussion Requests

https://discourse.wekan.io/t/teams-and-permissions/77 (somewhat similar)
https://discourse.wekan.io/t/any-progress-on-users-being-able-to-see-and-interact-all-boards-immediately-upon-registration-suggestion-groups/206

I currently don't know of any code bases that would assist in implementation of this feature, but this is the main reason why I'm still using Trello for my team, so I'd like to contribute. I did not see any pull request for it in the main repo. I know this would be a fairly heavy lift with database restructuring necessary.

If this isn't something someone currently has on their radar, I have forked this repo and will plan on documenting the technical requirements to implement this feature, and then communicate this and possibly start implementation of the feature as time allows.

Copied from original issue: wefork/wekan#52

Discussion

1 2 3 > >> (Page 1 of 3)
  • Anonymous

    Anonymous - 2017-02-08

    Originally posted by: xet7

    @aegrey

    This is related to other Wekan issues in this way:

    [#13] Has some code for admin interface, but probably does not include teams

    For making Wekan programmable, AFAIK there is no code for these yet:

    [#43] API

    [#42] Using Email with API

    [#49] Auto add user name to a moved card

    There is currently not much technical documentation of Wekan, only some related to using it at:
    https://github.com/wekan/wekan/wiki/FAQ
    https://github.com/wekan/wekan/wiki/Install-and-Update#install-manually-from-source

    Wekan code is mostly Javascript, templates, CSS and some YAML. It uses Meteor Javascript framework, Node.js for serverside, and MongoDB database that also is Javascript-based.

    On codebase, there is check for environment variable, is it running:
    1) Wekan standalone version, when it has multiboard features, login etc etc although disabling login on [#13] is not implemented yet.
    2) Running on Sandstorm, then only one board is in use and is set to public, because Sandstorm provides authentication, sandboxing in grains etc.

    Wefork code is quite logically divided to subfolders. I recommend that after cloning that repo to your computer:
    1) You don't add Node.js modules or Meteor framework to there
    2) Read the code and make notes

    If possible, it would be nice to have additional MongoDB database collections (or "tables" as in SQL database terms) for additional information added, that would make upgrading from previous versions of Wefork easier. Some users have a lot of data. So in new version if collection does not exists, then create it.

    Planning and documenting technical requirements would be a good way to start. This would also prevent duplicate work when Team/Organization admin is different than the simple previous [#13] implementation.

    Currently Wekan team is quite small, so having some new technical documentation of code structure would also help newcomers to get familiar with it.

     
  • Anonymous

    Anonymous - 2017-08-09

    Originally posted by: aegrey

    Thanks @xet7 - I've been looking over the code and am halfway through some tech specs for this, I've been busy but I'll post something when I put together something more solid if someone else doesn't take it on first. :)

     
  • Anonymous

    Anonymous - 2017-08-09

    Originally posted by: xet7

    @aegrey

    Thanks! It's very nice to get tech specs for this.

    Since your previous post to this issue Wekan has gained many more features, I will also add there recent ability to change email address.

     
  • Anonymous

    Anonymous - 2017-09-14

    Originally posted by: xet7

    Moved to here from [#1220]

    Feature request by @DukeW

    It would be nice to be able as an admin to take "ownership" of boards. I have a Wekan instance running for 30 people, and some people don't archive there boards when there done. I would like to be able to take ownership of these old boards and archive them my self. Also sometimes a board creator is not present and new people need to be added to a board, right now I don't have a way of doing this.

    Reply by @xet7

    It's possible to change you as board admin at MongoDB database, that link is mentioned at Platforms page. There is no Web UI for it yet. I have not tried can it be done with REST API.

     
  • Anonymous

    Anonymous - 2017-09-14

    Originally posted by: xet7

    @aegrey

    Can you add your in-progress tech specs to this issue?

     
  • Anonymous

    Anonymous - 2017-11-23

    Originally posted by: xet7

    @thuanpq is working on this.

    @thuanpq , please accept invitation to Wekan GitHub Organization so I can assign you to this issue.

     
  • Anonymous

    Anonymous - 2017-12-15

    Originally posted by: xet7

    Moved to here from [#1397]

    From @Logicbloke

    Hi,
    As a project manager, I sometimes have to dispatch task to team members, but I'm mostly using one board per project rather than one board per team member. Why is it that any member added to the board with the normal permissions can edit other cards other than the ones assigned to him? To the very list bring the permissions down to the lists level.

    The comment permissions look OK for this kind of thing but it's preventing the team member for ticking the checklists.

    Are kanban boards supposed to be one board per team member?

    Thanks!

    @Logicbloke

    Please add details how this feature would work step by step, and please add to bounty for this issue so there is enough funding for building these features, more details about bounties at http://www.xet7.org/wekan

     
  • Anonymous

    Anonymous - 2018-03-05

    Originally posted by: xet7

    Correction: ss+ is working on adding Teams/Groups feature.

    Afaik @thuanpq is not working on this feature.

     
  • Anonymous

    Anonymous - 2018-06-08

    Originally posted by: AndyatFocallocal

    I'm also actively following this issue. We weren't able to move from Trello as we needed the 'invite link' feature so visitors to our site could sign up and join a board. We haven't grown our dev team to the point where we can focus on building that feature, although we would join in your excellent work coding this project if we moved from Trello to Wekan

     
  • Anonymous

    Anonymous - 2018-06-08

    Originally posted by: xet7

    @AndyatFocallocal

    What 'invite link' feature? Please give link to existing or new issue about that.

     
  • Anonymous

    Anonymous - 2018-06-28

    Originally posted by: coolacid

    Re [#1737] Thanks for moving. I tried to see the best place. Subbed to this one. 👍

     
  • Anonymous

    Anonymous - 2018-07-03

    Originally posted by: d3dbit

    I am also interested in this feature.

     
  • Anonymous

    Anonymous - 2018-07-20

    Originally posted by: xet7

    If all goes well, I'll maybe get teams feature from ss+ next week, so I'll add this note to myself so I'll check 2018-07-27 did it happen.

     
  • Anonymous

    Anonymous - 2018-08-28

    Originally posted by: xet7

    I have some parts of teams feature in progress at https://github.com/wekan/wekan/tree/feature-teams . It still needs some work, Admin Panel part is not visible currently, etc.

     
  • Anonymous

    Anonymous - 2018-12-03

    Originally posted by: xet7

    Moved to here from https://github.com/wekan/wekan/pull/2029

    From @saurabharch

    Admin can create credential of new user of team member and bypass the user verification, bcz some email transactional process is not working well so need new features like this.

    @saurabharch Do you mean adding new user in Admin Panel ?

     
  • Anonymous

    Anonymous - 2018-12-26

    Originally posted by: mpathiuk

    I'd also like to be able to add new users in admin panel. As admin it would be good to be able to change 'verified' for email to 'yes' in the backend in the edit screen too.

     
  • Anonymous

    Anonymous - 2019-01-10

    Originally posted by: luke5sky

    @xet7 is there a workaround for deleting a user? Thank you for your help

     
  • Anonymous

    Anonymous - 2019-01-11

    Originally posted by: xet7

    @luke5sky

    I would recommed disable user using API.

    It's also possible to take ownership of users boards but it's not documented well yet.

    It's not recommeded to delete user because it can break Wekan board.

    What should happen to user's data when user is deleted? It's not implemented properly yet.

     
  • Anonymous

    Anonymous - 2019-02-27

    Originally posted by: ChargingBulle

    My Team would greatly benefit from this.
    When will it roll out?

     
  • Anonymous

    Anonymous - 2019-02-27

    Originally posted by: rterwedo

    @xet7 Whats the target bounty for this?

     
  • Anonymous

    Anonymous - 2019-02-27

    Originally posted by: xet7

    @rterwedo

    $700 so I can start

     
  • Anonymous

    Anonymous - 2019-02-27

    Originally posted by: rterwedo

    @xet7 I can try and get approval for some of it, but will take sometime.

     
1 2 3 > >> (Page 1 of 3)

Log in to post a comment.