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

Confusion in determining an Active/Inactive team member #338

Open
swatyshah opened this issue Apr 13, 2017 · 1 comment
Open

Confusion in determining an Active/Inactive team member #338

swatyshah opened this issue Apr 13, 2017 · 1 comment
Assignees

Comments

@swatyshah
Copy link

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting.
[ ] feature request =>

Step/s to reproduce issue

In Scrum Bot I observed that if we mark a member inactive then the bot won't ask any question to that team member. But I do not get any option to mark a person inactive. Additionally, I am confused that if I mark a person Inactive, will he become Inactive in all projects or do I have the facility to do so project-wise?

With my experience, I would prefer to have a feature of marking a person inactive project-wise as there are certain roles eg., Designer who are not required to actively participate throughout the project duration.

Screen shot

@juliepromact
Copy link
Collaborator

But I do not get any option to mark a person inactive.

A person can be marked Inactive from Oauth-Server by unchecking the Status checkbox in User Edit page.

Additionally, I am confused that if I mark a person Inactive, will he become Inactive in all projects or do I have the facility to do so project-wise?

At present if a user is marked Inactive, he/she will be inactive in all the projects. If a person is not required in a project he/she can be removed from the project and added as and when needed.

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