The problem
The tmpo manual command ignores the --project flag when resolving the hourly rate. It currently pulls the rate exclusively from settings.FindAndLoad() (the nearest .tmporc). This means global projects never get their configured rate applied to manual entries. Furthermore, if a user runs tmpo manual --project "Global Project" while inside a directory containing an unrelated .tmporc, the manual entry incorrectly inherits the local directory's rate.
Release version
0.8.6
Operating system
macOS
Steps to reproduce the behavior
- Initialize a global project with an hourly rate:
tmpo init --global
- Run
tmpo manual --project "Your Global Project" and create an entry.
- Check the entry stats. The hourly rate will be
0 (or the rate of the local directory if executed inside one with a .tmporc).
Screenshots
No response
Additional context
cmd/tracking/start.go handles this correctly using project.GetProjectConfig(projectName). manual.go should be updated to use this same logic to resolve the rate.
The problem
The
tmpo manualcommand ignores the--projectflag when resolving the hourly rate. It currently pulls the rate exclusively fromsettings.FindAndLoad()(the nearest.tmporc). This means global projects never get their configured rate applied to manual entries. Furthermore, if a user runstmpo manual --project "Global Project"while inside a directory containing an unrelated.tmporc, the manual entry incorrectly inherits the local directory's rate.Release version
0.8.6
Operating system
macOS
Steps to reproduce the behavior
tmpo init --globaltmpo manual --project "Your Global Project"and create an entry.0(or the rate of the local directory if executed inside one with a.tmporc).Screenshots
No response
Additional context
cmd/tracking/start.gohandles this correctly usingproject.GetProjectConfig(projectName).manual.goshould be updated to use this same logic to resolve the rate.