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

[RFE] hierarchical projects #177

Open
hgkamath opened this issue May 26, 2023 · 1 comment
Open

[RFE] hierarchical projects #177

hgkamath opened this issue May 26, 2023 · 1 comment

Comments

@hgkamath
Copy link

hgkamath commented May 26, 2023

Firstly, thanks for developing the opensource time-tracking tool.
I was trying out your PWA, and it got me thinking.

Presently in the 'task add' dialog, one can't add a whole project as a task of another.

I was thinking of having a "life" project as a top level, and say have other life-roles being tasks, and projects in those roles being tasks of others.
Does this use-case fit in with your roadmap for titra.

Some things to consider

  • A single person does not work on two projects at the same time, though members of a team might.
  • Visualization
    • The inner details/time-allocations of a sub-project are not visible in the graph of a higher level project.
    • One should be able to click through, ascend/descend parent/child projects
  • Time spent by default is supposed to accumulate to a higher level project, perhaps configurable to not do so.
  • Billing by default does not accumulate to a higher level project, perhaps configurable to do so.
  • Projects may not form a cycle. One way to avoid cycles is to have project levels, wherein a project with a level no (ex 3), can only add a project as a task, if that project is assigned a larger numerical level (ex 4,5 .. )
  • While a project may be usually a task of only one other project, perhaps it can additionally be a task of several projects.
  • A project may not be archived/deleted while it is still a task of another project.
@faburem
Copy link
Collaborator

faburem commented May 26, 2023

Interestingly this has already been requested a couple of times before. So far we didn't have the capacity to work on it but since we have a bigger team now we will discuss the feasibility in our next Sprint meeting. Thanks for explaining your use case in detail!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants