Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Worker role, that can move and comment cards (a worker rule) without the ability to edit/create/delete cards #2788

Closed
nickbe opened this issue Nov 8, 2019 · 9 comments
Assignees

Comments

@nickbe
Copy link

nickbe commented Nov 8, 2019

Just that. A typical worker should not have the right to edit/delete any cards, but of course he/she should make changes to the status. Which means being able to move the card between columns.

@xet7
Copy link
Member

xet7 commented Nov 12, 2019

You are the first one that has asked for that kind of role. I don't know everybody's use cases.

Anyone can add new role to Wekan with pull request. So you can make fork of Wekan, add changes, git commit, git push, at GitHub website click create pull request.

For example in roles issue #1861 , I added "No comments" role this way 77efcf7 . So there is ready-made example already.

Role docs are at wiki.

Before using Role API, you need to get Bearer token by logging in as Admin user as form data.

@nickbe
Copy link
Author

nickbe commented Nov 15, 2019

Well I'm not experienced with wekans' programming so forking wouldn't make much sense for me.
But the role seems to obvious that I'm astonished no one asked for it before.

If you have work team and you're the team leader, then you're also the one who creates the cards, assigns them to the team members and who is monitoring their progress.

You don't want them to move the cards - or delete them - because as a team leader it's yout reposibility to decide when a card has to be moved, archived and so on.....

Therefore you would need a worker role. And a worker would only be able to see is cards and comment then.

@xet7
Copy link
Member

xet7 commented Nov 15, 2019

I can implement worker role if someone pays 250 euro for my coding time at:
https://wekan.team/commercial-support/

@nickbe
Copy link
Author

nickbe commented Nov 19, 2019

Ok, done - here's the sumary of "worker role":

Can: move cards, can assign himself to card, can comment,
Cannot: anything else including revoke card, change settings, create/delete/edit cards/tags and so on...

@xet7 xet7 changed the title Why is there no role that can move and comment cards (a worker rule) without the ability to edit/create/delete cards Worker role, that can move and comment cards (a worker rule) without the ability to edit/create/delete cards Nov 28, 2019
@xet7 xet7 self-assigned this Nov 28, 2019
@nickbe
Copy link
Author

nickbe commented Dec 2, 2019

Hi Lauri,
might I have a quick status update?

@xet7
Copy link
Member

xet7 commented Dec 2, 2019

@nickbe

Currently I have many features on my todo list so I presume this worker rule feature will be ready sometime at this month December.

@nickbe
Copy link
Author

nickbe commented Dec 4, 2019

Ok thanks. I'll inform my team.

@xet7 xet7 closed this as completed in 2bf0041 Jan 3, 2020
@xet7 xet7 reopened this Jan 3, 2020
@xet7
Copy link
Member

xet7 commented Jan 3, 2020

I did add worker role, and then remove it, because there was some bug when saving card. I'm currently in progress of fixing it.

If you like, you can test in-progress worker role on these docker tags, but I recommend waiting when I have fixed that card save bug.

  • quay.io/wekan/wekan:v3.59
  • wekanteam/wekan:v3.59

You will see on ChangeLog when I get it added back:
https://github.com/wekan/wekan/blob/master/CHANGELOG.md

@nickbe
Copy link
Author

nickbe commented Jan 4, 2020

Happy new year Lauri 🍾

We'll wait until the finished version is live and updatable via snap on our server,
Thanks for reporting back and working on it. This feature will come in very handy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants