Skip to content
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

Filter-aware summary/location field #199

Open
Terrance opened this issue Jul 5, 2024 · 0 comments
Open

Filter-aware summary/location field #199

Terrance opened this issue Jul 5, 2024 · 0 comments

Comments

@Terrance
Copy link

Terrance commented Jul 5, 2024

Having come from time tracking via iCalendar, the main thing I'm missing is the separation of summary (i.e. title), location and description information. Preparing to migrate existing entries from there, I've been through and categorised them (which will map to activities), and I was planning on just combining all the text information into comments. However, whilst tracking current events in STT, I've found it a bit clumsy to try and juggle all this info in a single field.

I have a handful of somewhat generic activities (such as Admin, Chore, Game, Tinker) where I've consistently included a comment for the actual task at hand, but some of these have additional notes only relevant to that instance underneath. Other activities are location-based (Event, Meal etc.) and I've been writing the location in the comments field, but sometimes other activity types could do with a location in addition to a summary or note.

The recent comment selection of course just offers the whole thing from past events -- as this is per-activity the usage at least tends to be consistent, though for some there are bits of notes I have in some entries that are only relevant to individual entries, but a common summary or location that I would still like to use as a base. It's also not really queryable/filterable outside of bulk-editing (e.g. it would be handy to filter for locations or get a breakdown of tasks and chores).

What would be useful is a separate summary field (intended to be a single line but otherwise free text, which potentially can be used in the stats screen, and where past values are likely to be reused and useful to suggest) alongside comments (for additional commentary that likely need not be reused or queried directly).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant