Feature Request: At each board, have board-specific roles

Brought to you by: wekan

#1861 Feature Request: At each board, have board-specific roles

Status: closed

Owner: nobody

Labels: None

Updated: 2021-01-12

Created: 2018-08-28

Creator: Anonymous

Private: No

Originally created by: xet7
Originally owned by: xet7

Roles should have:

Role name, example: client
Role permission, example: Admin / User / Comment only / No comments
Role color, that is round line around the avatar image

For each user on board, when role is selected from list, all role properties are applied.

Only board Admin can change roles.

Discussion

Anonymous - 2018-08-28

assigned_to: xet7
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2018-08-28

Originally posted by: therampagerado

Yes, this is a must.

The roles must be editable so everybody can add or remove roles and each action in the kanban should have settings in this area - from moving cards, to deleting lists, boards, etc. At the moment everybody can do virtually everything with the board, deface and ruin the work of many in the company and even stop work at all.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2018-08-31

Originally posted by: xet7

@rhelsing

In your Comment only permissions PR https://github.com/wekan/wekan/pull/925 what does this mean?

models/lists.js:

return allowIsBoardMemberNonComment(userId, Boards.findOne(doc.boardId));

What does it do?

Did you name it correctly? Or, should is be renamed to something more descriptive?

Do you already have permissions for No comments somehow? So for that users comments are not shown?

Some related PRs here:
https://github.com/wekan/wekan/pulls?q=is%3Apr+permission+is%3Aclosed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2018-08-31

Originally posted by: rhelsing

I believe all references to 'allowIsBoardMemberNonComment' should be changed to 'allowIsBoardMemberNonCommentOnly' to be more descriptive even though that is a bit more verbose. It could be refactored to 'allowIsBoardMemberCommentOnly' to be cleaner descriptively, but that would require more (possibly bug inducing) changes to the codebase. I believe I named it that to be as minimally intrusive as possible to the existing codebase.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2018-08-31

Originally posted by: xet7

Yes, CommentOnly would be much more descriptive, because current NonComment can be easily confused when I add NoComments. I will look how to make the change.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2018-08-31

Originally posted by: xet7

Currently at Wekan code, problem is not to do the least intrusive change. More important is to make code clearer and have consistent naming. For example, there is still references to archives in code and database, it should be renamed to recycle bin like it's at translations already.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2019-04-12

Originally posted by: xet7

Roles for more hidden fields, and add role selection to admin panel [#802]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2021-01-12

Originally posted by: xet7

Moved to [#3022]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Anonymous - 2021-01-12

Ticket changed by: xet7

status: open --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.