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.

Sign up for GitHub

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

Jump to bottom

Bug when existing project hours user doesn't have 'can_clock_in' permission #813

Open
ghost opened this issue Dec 5, 2014 · 0 comments
Open

Bug when existing project hours user doesn't have 'can_clock_in' permission #813

ghost opened this issue Dec 5, 2014 · 0 comments
Labels
bug

Comments

@ghost
Copy link

ghost commented Dec 5, 2014

The schedule edit page doesn't render correctly if a ProjectHours user somehow doesn't have the can_clock_in permission.

If a user that has associated ProjectHours somehow loses the can_clock_in permission, they are not included in the all_users data sent to the front end, and a JavaScript error occurs.

Workaround for now is for all users who have ever had ProjectHours to keep the can_clock_in permission. Their user account can be set to active = False if they leave the company, which prevents them from logging in or clocking time.
@ghost ghost added the bug label Dec 5, 2014
@ghost ghost changed the title Project hours bug when existing project hours user doesn't have 'can_clock_in' permission Bug when existing project hours user doesn't have 'can_clock_in' permission Dec 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants