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

Display weekly allocation on employee detail pages #1629

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

Display weekly allocation on employee detail pages #1629

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

Comments

@jduss4
Copy link
Contributor

jduss4 commented Jun 13, 2023

When viewing an employee's detail page (/employees/[user.email]), you can look at a breakdown of the hours spent on each project line across several weeks. If there was no timecardobject (entry) for a project on a particular week, it will display 0. If weekly allocation was added, it will display as None.

When "None" hours are displayed, it becomes difficult to understand how much time a person actually spent on each project. See below, where I was tocking 100% to the delivery assurance team and billing 12.5% to the dev tools team, but this is not clear from the table.

This issue may require product and design work to understand what information different users need from this display, and then determine how best to change the detail page to present that information.

Note: This part of the code is iterating over timecardobjects, meaning that they bear weekly allocation % but no easy way to convert them to an hourly equivalent (without relying on other timecardobjects associated with the linked timecard, for example OOO time).

image

[example of project table with multiple projects across weeks. the Dev Tools and Delivery Assurance lines say None for each week, while other entries have hours]

@jduss4 jduss4 added the design label Jun 13, 2023
@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

3 participants