[GH-ISSUE #4083] [FR] Time field type #1835

New issue

Closed

opened 2026-03-23 21:17:36 +00:00 by mirror · 3 comments

mirror commented

2026-03-23 21:17:36 +00:00

Owner

Originally created by @zoli on GitHub (Dec 4, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4083

Originally assigned to: @zoli on GitHub.

Description

A field type for determining time like 20 minutes, 3 hours, etc. It's useful for task management purposes, To show how much time a task needs or how much I've spent time on the task.

Impact

Users who use the Kanban or grid view for managing tasks or similar stuff.

Additional Context

I would like to implement this my self if its an acceptable feature.

Originally created by @zoli on GitHub (Dec 4, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/4083 Originally assigned to: @zoli on GitHub. ### Description A field type for determining time like 20 minutes, 3 hours, etc. It's useful for task management purposes, To show how much time a task needs or how much I've spent time on the task. ### Impact Users who use the Kanban or grid view for managing tasks or similar stuff. ### Additional Context I would like to implement this my self if its an acceptable feature.

mirror

2026-03-23 21:17:36 +00:00

closed this issue
added the
plugins

database

new feature
labels

mirror commented

2026-03-23 21:17:36 +00:00

Author

Owner

@Xazin commented on GitHub (Dec 4, 2023):

In project management, eg. scrum, you'd most likely be using something similar to days, t-shirt sizes, or story points.

As these are arbitrary, it's up to the "team" to define what these mean, or how to put down estimations.

I reckon a Single Select Option is fine for this purpose.

For your specific use-case, you can have some preset time estimates using Single Select Option, eg. [30 mins, 1 hour, 4 hours, 1 day, 2 days, 1 week, 2 weeks] and another text field with the actual time spent for comparison.

If we can come up with a good design for this field type, I believe it would still have value.

@Xazin commented on GitHub (Dec 4, 2023): In project management, eg. scrum, you'd most likely be using something similar to `days`, `t-shirt sizes`, or `story points`. As these are arbitrary, it's up to the "team" to define what these mean, or how to put down estimations. I reckon a `Single Select Option` is fine for this purpose. For your specific use-case, you can have some preset time estimates using Single Select Option, eg. `[30 mins, 1 hour, 4 hours, 1 day, 2 days, 1 week, 2 weeks]` and another text field with the actual time spent for comparison. --- If we can come up with a good design for this field type, I believe it would still have value.

mirror commented

2026-03-23 21:17:37 +00:00

Author

Owner

@zoli commented on GitHub (Dec 4, 2023):

Thank you for the insights, Mathias.
Maybe for project management that will be fine (not all the cases though). But not for personal task management. Also, it won't work for how much I've spent time. For example, the estimate is 4 hours but I've spent 1.5 and I want to submit it and continue from that later on.
Besides the above notes I also was thinking maybe in the future it will be possible to have time tracking within AppFlowy, I hit a button and it starts tracking time spent on a specific card until I hit the button again. This needs a continuous field instead of STH discrete like Single Select.
Another possible future could be AppFlowy supporting some sort of scripting or functions in Grid cells so it can show the total time that all the tasks in the grid took and the total time the user has spent on tasks or within this week, etc. This also needs a field that stores data as a number.

I was thinking of a field type similar to number field type with some extra display option for showing the time in the frontend (similar to date field display options).

@zoli commented on GitHub (Dec 4, 2023): Thank you for the insights, Mathias. Maybe for project management that will be fine (not all the cases though). But not for personal task management. Also, it won't work for how much I've spent time. For example, the estimate is 4 hours but I've spent 1.5 and I want to submit it and continue from that later on. Besides the above notes I also was thinking maybe in the future it will be possible to have time tracking within AppFlowy, I hit a button and it starts tracking time spent on a specific card until I hit the button again. This needs a continuous field instead of STH discrete like Single Select. Another possible future could be AppFlowy supporting some sort of scripting or functions in Grid cells so it can show the total time that all the tasks in the grid took and the total time the user has spent on tasks or within this week, etc. This also needs a field that stores data as a number. I was thinking of a field type similar to number field type with some extra display option for showing the time in the frontend (similar to date field display options).

mirror commented

2026-03-23 21:17:37 +00:00

Author

Owner

@Xazin commented on GitHub (Dec 4, 2023):

Thank you for the insights, Mathias. Maybe for project management that will be fine (not all the cases though). But not for personal task management. Also, it won't work for how much I've spent time. For example, the estimate is 4 hours but I've spent 1.5 and I want to submit it and continue from that later on. Besides the above notes I also was thinking maybe in the future it will be possible to have time tracking within AppFlowy, I hit a button and it starts tracking time spent on a specific card until I hit the button again. This needs a continuous field instead of STH discrete like Single Select. Another possible future could be AppFlowy supporting some sort of scripting or functions in Grid cells so it can show the total time that all the tasks in the grid took and the total time the user has spent on tasks or within this week, etc. This also needs a field that stores data as a number.

I was thinking of a field type similar to number field type with some extra display option for showing the time in the frontend (similar to date field display options).

Hmm, I'd love to see this in practice, I can't really come up with an especially good way of visually representing these options, but I'm sure you'll figure something out :D

I've assigned you, maybe this can lead to some more interesting types of fields in the future as well.

@Xazin commented on GitHub (Dec 4, 2023): > Thank you for the insights, Mathias. Maybe for project management that will be fine (not all the cases though). But not for personal task management. Also, it won't work for how much I've spent time. For example, the estimate is 4 hours but I've spent 1.5 and I want to submit it and continue from that later on. Besides the above notes I also was thinking maybe in the future it will be possible to have time tracking within AppFlowy, I hit a button and it starts tracking time spent on a specific card until I hit the button again. This needs a continuous field instead of STH discrete like Single Select. Another possible future could be AppFlowy supporting some sort of scripting or functions in Grid cells so it can show the total time that all the tasks in the grid took and the total time the user has spent on tasks or within this week, etc. This also needs a field that stores data as a number. > > I was thinking of a field type similar to number field type with some extra display option for showing the time in the frontend (similar to date field display options). Hmm, I'd love to see this in practice, I can't really come up with an especially good way of visually representing these options, but I'm sure you'll figure something out :D I've assigned you, maybe this can lead to some more interesting types of fields in the future as well.

mirror referenced this issue

2026-03-23 22:16:37 +00:00

[PR #1835] [MERGED] Feat/appflowy tauri #4965