-
Notifications
You must be signed in to change notification settings - Fork 5
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
New feature: Templates #7
Comments
Elaborating more on this (thinking about it, will evolve...)When starting a new estimate I have an option of selecting from a list of existing estimates, created once and (all of them) marked as "templates" (and thus persistent). When pressing the "+" button the first thing I must specify is a "task name" as a string. Here I could have a "suggested" list of existing tasks that come from the mentioned template I choose to adopt at the beginning. Of course I still have a chance of writing a task from scratch instead of using a template (simply write a new name instead of ocnfirming from templates. Should also have a chance of modifying anything from the template. Template == only filling the fields at edit time (no further link between a created task and the template it was created from)?? |
I am not entirely clear about what the template functionality should do. I take it simply copying another project isn't enough? Either way, it would require support for user and organization accounts if your templates should be available in a list. |
Copying an existing project could be an easy solution yes. But; in my vision, templates for the single tasks should exist, not for the entire project |
I just estimated my first project and really like the concept. I'd like to be able to copy this project and edit the copy as an alternate estimate. This type of templating would be sufficient for my current and foreseeable use-cases. Thanks. |
Templates
So that I can prepare descriptions for tasks I often use in my quotations and select from a drop down when adding a new task.
The text was updated successfully, but these errors were encountered: