Who's the anonymous person taking this on? I'd really like to see this functionality, and I was about to jump into it when I noticed it was assigned.

Updating tickets (#743, #752, #768, #781, #535, #47, #295, #298, #805, #806, #324, #584, #97, #592, #344, #603, #114, #629, #636, #645, #393, #405, #433, #434, #202, #462, #220, #233, #310, #95, #635, #397, #94)

I've implemented this for my own purposes but got stuck on some UI stuff. Check out http://github.com/epall/tracks/commits/master for my changes.

look promising. Where are you stuck?

I'm not sure about the migration. Why not use the tagging mechanism in tracks? It is more difficult, but it makes sure all tags are handled the same (future tag controller for tag management?)

Hmm. I hadn't thought about actually tagging projects. Good idea!

As for the stuck, I was trying to do an autocomplete for the default tag entry and it turned out to be pretty challenging. I ended up implementing just enough to get by and moving on.

So, I'll try switching to tagging projects and then merge to core tracks?

for tagging we need to look into a good design so that tagging projects (other enhancement request) is possible. So actually you want to be able to tag a project twice: once for the default tags of the todos in the project and once to tag the project itself

I think there is a way to use autocomplete for multiple entries. There is a separate ticket for this, so perhaps you can postpone autocomplete for tags for that other ticket?

Yes, if you get tagging to work, do merge :-)

I've looked at has_many_polymorphs and I cannot find a way to put two sets of tags on the same model. So either we stick to your solution for the default tags (i.e. a string) or we need to create a new model (1-1 relation to project) to which we can stick the default tags.

I think I prefer the string solution: its simpler and will do fine for now. What do you think?

(In revision:42bea2490bfbf12797c9e0beb7294b13b11b16d1) Fix #592 be able to set default tags for a project. Default tags can now be specified when creating or editing a project, and they will be applied to any new todos created in that project.

Branch: master

I've been using the string solution for a few weeks now and I'm happy with it. Merging and closing the ticket for now.

Cool stuff. I need to get this rspec stuff going for myself too :-)

(In revision:42bea2490bfbf12797c9e0beb7294b13b11b16d1) Fix #592 be able to set default tags for a project. Default tags can now be specified when creating or editing a project, and they will be applied to any new todos created in that project.

Branch: master