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

give each sow/allocation its own hours #37

Open
bburdette opened this issue Feb 3, 2023 · 0 comments
Open

give each sow/allocation its own hours #37

bburdette opened this issue Feb 3, 2023 · 0 comments

Comments

@bburdette
Copy link
Contributor

Just an idea - could address the issue with pay rate changing from one SOW to the next.

Instead a project being a bucket for all the hours work, each SOW ('allocation' in timeclonk terminology) gets its own hours, separate from other sows. So you navigate into a project and then into a sow to add hours.

  • outpost-space
    • SOW1
      • hours
    • SOW2
      • hours
    • SOW3
      • yet more hours

That would also address the current issue of the hourly rate changing from one sow to another. As of now timeclonk assumes a constant pay rate for the whole project.

Another issue addressed here would be how to deal with projects with multiple years worth of hours entries. So far it hasn't been an issue, but one of these days a project will get too many hour entries and get sluggish.

It would be slightly more hassle than the current monobucket of hours approach, but the UI could probably navigate to the right sow automatically.

@bburdette bburdette reopened this Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant