timo I was not able to reproduce the problem. Can you maybe add some screenshots that visualize it? You can not add "custom value tags" to a task because custom value tags always require the manual input of the user and this is not always possible when creating a new work unit (because for example, new work units can be created "outside" the app, using the notifications etc).
artz Came here for the same problem, I am running the Pro version on Windows 11. I created two test tags, one default and the other custom. Custom tag: When creating a new task, the custom tag does not display:
artz Hmm, I'm sorry but could you please explain how to add a custom tag value to a work unit? I imagined using it when creating Tasks, as at that point to use your example you could specify what "client" the work is for.
timo To add it to a work unit, either click on it on the list and use the "Add tags" button or right click the work unit and use "Add tags" in the context menu
artz timo Thanks! I got it now. My main point of confusion was around adding it to Work Units vs. Tasks. In your example of creating a "clients" tag, I would have expected the ability to associate Tasks to a particular client, that way I would not have to tag every work unit after the fact, as Tasks can span multiple sessions.
timo You can associate "normal" tags to tasks, so that you don't have to add them manually for each work unit. The only reason this is not possible for "custom" tags is because they require user input
artz timo right, I understand. I am still unsure why there is a philosophical or technical limitation in adding the additional tag metadata at the time of Task creation, and inherited by the Work Units (as the default tags are) when they are created based on the Tasks. I just started using this app but that would seem like a big time saver as my client and project list grows, tags could be a way to add additonal facets without bloating the number of tags.
timo I think I understand what you mean. So you have a "client" custom tag and you have a "project X" task and ever time you work on "project X" it is for one specific client. So you would want to add the name of the client when adding the tag to the task, and this client tag+name is then used every time you work on that task. Right? I will see if this would be possible from what the database schema offers right now or if it would require a change.
timo Unfortunately the database schema doesn't currently have a column that could be used to save this data. I noted down your suggestions so when I do the next database migration, this would be included.
artz Hey @timo! just following up on this request, if you formally added it to a future release and have a date in mind. Thanks!