Interesting. But I'm not sure if this fits Tracks as a task management app though.

I would tend to disagree -- as I see it, part of task-management is task-definition, and to be able to define tasks visually (e.g. tasks like implementing a given software architecture, or researching some visually-represented idea) provides much more power when specifying the task. Lets say I have an idea my mind which represents a certain mechanical design, and my task is to try to implement / completely specify the design. Then having a way of recording the initial concept would be beneficial when specifying the task. One could argue that this can be done separately with a different application, and you can refer to the created document -- this has several disadvantages - 1) the document might get moved / deleted somehow, 2) you have several additional steps in order to create the document, store it, link it (and the inverse when you want to view the document after looking at a task), 3) if Tracks will ever be used in the future in a collaborative way (i.e. with shared tasks / etc.), it makes a lot more sense to store notes like this directly in Tracks.

Ultimately, an SVG drawing/diagram is a superset of what you can represent with text. If you imply that this isn't relevant/useful for 'task management', then this assumes that you can imagine all of the possible ways that tasks can be managed. This, however, is difficult for any person to do, and adding the extra functionality could enable new ways which hadn't even been considered before.

I'm more inclined to add generic attachments to todos/projects. That way you can add and share all sorts of objects.

Related association with ticket #535 was added

Migrated to GitHub issue #1057