You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Project detail pages (/projects/[project_id]) are set up to expect projects with hourly billing. Projects that use weekly allocation amounts do not have a chart to represent their time and the "hours summary" looks as though no work has been done.
It may be difficult to estimate an hourly equivalent spent on a project due to the timecardobjects lacking information about a person's OOO time, but options include using a snazzy query to put together more accurate information, creating a crude ballpark estimation, or altering the display to provide other metrics about a project besides hours spent.
This would benefit from product and design attention.
[Example of a project with hourly billing. It has total hours and a chart of user hours]
[Example of a project with weekly billing. It has 0 hours, no chart, and the sentence "We'll put a chart here once hours have been tocked to this project"]
The text was updated successfully, but these errors were encountered:
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.
Project detail pages (
/projects/[project_id]
) are set up to expect projects with hourly billing. Projects that use weekly allocation amounts do not have a chart to represent their time and the "hours summary" looks as though no work has been done.It may be difficult to estimate an hourly equivalent spent on a project due to the timecardobjects lacking information about a person's OOO time, but options include using a snazzy query to put together more accurate information, creating a crude ballpark estimation, or altering the display to provide other metrics about a project besides hours spent.
This would benefit from product and design attention.
[Example of a project with hourly billing. It has total hours and a chart of user hours]
[Example of a project with weekly billing. It has 0 hours, no chart, and the sentence "We'll put a chart here once hours have been tocked to this project"]
The text was updated successfully, but these errors were encountered: