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

Remove employee.expected_project_allocation #1632

Open
jduss4 opened this issue Jun 13, 2023 · 1 comment
Open

Remove employee.expected_project_allocation #1632

jduss4 opened this issue Jun 13, 2023 · 1 comment
Labels

Comments

@jduss4
Copy link
Contributor

jduss4 commented Jun 13, 2023

The UserData model has a field, expected_project_allocation which appears to be unused. While the production data has values, they are mostly "1" and occasionally are somewhat inconsistent, with values like .6 and .5, and users with a 0 billable expectation still assigned a "1" expected allocation.

As we already have a field for expected_billable_hours from which one can derive an expected allocation, I recommend that this field is removed. However, it is not currently hurting anything where it is, either. I'm opening this issue as a space for discussion!

https://github.com/18F/tock/blob/main/tock/employees/models.py#L87

@MelissaBraxton
Copy link

Weighing in from the TLC Crew:

We think this is a good idea but it doesn’t currently fit with our near- or mid-term roadmap. This means we will not work on this in the next 3 months. We will revisit this in 3 months and check in then. In the meantime, if you find another way to get this work done feel free to choose that path. If you do find a different path to getting the work done and no longer want TLC crew help, please remove the issue from our project board.

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

No branches or pull requests

2 participants