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

[FR] Time field type #4083

Closed
zoli opened this issue Dec 4, 2023 · 3 comments · Fixed by #5349
Closed

[FR] Time field type #4083

zoli opened this issue Dec 4, 2023 · 3 comments · Fixed by #5349
Assignees
Labels
database the underlying data of grid, kanban, cal new feature New feature or request plugins this is a plugin task

Comments

@zoli
Copy link
Contributor

zoli commented Dec 4, 2023

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.

@Xazin
Copy link
Collaborator

Xazin commented 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.

@zoli
Copy link
Contributor Author

zoli commented 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).

@Xazin
Copy link
Collaborator

Xazin commented 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 Xazin added the new feature New feature or request label Dec 4, 2023
@annieappflowy annieappflowy added database the underlying data of grid, kanban, cal plugins this is a plugin task labels Dec 20, 2023
@zoli zoli mentioned this issue May 16, 2024
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
database the underlying data of grid, kanban, cal new feature New feature or request plugins this is a plugin task
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants