Skip to content

give each sow/allocation its own hours #37

@bburdette

Description

@bburdette

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions