Allow tracking tomatoes for individual projects

[dielsalder]

The way projects and tags are currently implemented, projects are organized under tags, and when the user completes a tomato they are prompted to fill in tags.

This means that if you have a tag "tomatoes" and projects called "fix issue 60" and "fix issue 61", then you're allowed to log a tomato under the "tomatoes" tag, but it will apply to both projects. This doesn't make much sense if you've fixed issue 60 and not issue 61.

It would be useful to clearly separate tracking for tags and projects, and to allow logging tomatoes for single or multiple projects. Tomatoes logged for tagged projects would also be tracked for the appropriate tags, and in addition users would be able to log tomatoes to a tag but no specific projects. Thoughts?

[LeBaux]

I agree, whole tags implementation is confusing, especially without any tomato.es documentation. It should be tasks. For example I am working on two website projects, but they have the same tags, so tracking them is impossible.

website1.com

• wireframing
• layout
• coding
• email and corespondece with client
• copywriting

website2.com

• wireframing
• layout
• coding
• email and corespondece with client
• copywriting

[potomak]

Just use one tag for the project, example: website1, website2; and the other to track your activity, example: wireframing, layout, etc.

See #34 (comment)

I agree about the lack of documentation, contributions to #83 would be appreciated.

[krysjez]

@potomak Is there any interest in doing a small redesign of the site? I think tomato.es is a great idea but the UX is a little lacking.

[potomak]

@krysjez yes, @pinakes was working on a redesign that was also responsive, see https://github.com/potomak/tomatoes/tree/feature/restyle.

I'd be glad to get help about that, so feel free to fork the project and send a PR to start the redesign process. Contact me if you need help.

[potomak]

@dielsalder I'd like to close this issue because in my opinion it doesn't apply.

Tomatoes and projects are associated in a dynamically, that's the most interesting behavior of tags. The easiest way to uniquely associate a tomato to a project is for each project to have a unique tag and to track tomatoes that include that unique tag to associated them to the project.

The example proposed by @LeBaux is perfect. In this case I would create those two main projects with the tags:

website1.com

• tags: website1

website2.com

• tags: website2

Let's say that I spend

• 10 tomatoes wireframing website1.com; tags: website1, wireframing
• 5 tomatoes coding website1.com; tags: website1, coding
• 8 tomatoes wireframing website2.com; tags: website1, wireframing
• 4 tomatoes coding website2.com; tags: website2, coding

I would end up respectively with:

• 15 tomatoes tracked under the website1.com project
• 12 tomatoes tracked under the website2.com project

If I want to see how much time I spent doing only one thing across all of my projects, for instance all the tomatoes I spent coding, or one thing relative to one project only, I would create another set of secondary projects, for instance:

Coding

• tags: coding
• 18 tomatoes (10 from website1.com, 8 from website2.com)

Wireframing

• tags: wireframing
• 9 tomatoes (5 from website1.com, 4 from website2.com)

website1.com coding

• tags: website1, coding
• 10 tomatoes

website1.com wireframing

• tags: website1, wireframing
• 5 tomatoes

What do you think about this approach?
What could we do to make it more clear or easier to understand?
Is there any use case that I missed?

[rschuetzler]

If I'm understanding what you've proposed here, that doesn't match with how I think about a project. I project, both in real life and in time tracking software, should be a collection of a bunch of tasks, possibly a variety of them. Here's how I feel would make sense:

• Creating and adding tomatoes to a project works just like it is right now. I create a project-specific tag, and then use that tag for all tomatoes related to that project. E.g., dissertation, website, or datacom-class
• Other tags are added to the tomato to represent what I actually worked on. E.g., writing, coding, revisions, studying.
• The "tags" page can be used to see how much time was spent on coding or writing across all projects.
• The "project" page should show a breakdown by tag of the tomatoes associated with that project. E.g.:

Tracked tomatoes: 4
   writing: 3
   coding: 1

• Ideally this would also include a breakdown by time, allowing me to see how much time was spent on a given project over time, and how much on various tags over time as well. See Week-by-week tracking? #294 for my request about more detailed time-based reporting.