github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-09 21:37:51 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[FR] - Possibility to create tasks also in Table-View instead only in List #2139

New Issue
Open
opened 2026-03-22 13:56:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 13:56:17 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by PewQuadrat on 2022-07-19T11:01:17.000Z

Hello,

it would be nice if we could also create Tasks from the Table view. In all other list types there is a least a button.

Greetings

Original issue on Gitea

Bouni commented on 2022-08-17T08:51:44.000Z:

Exactly what I need as well! If I find some spare time, I'll submit a PR for this ...

dpschen commented on 2022-09-26T13:04:12.000Z:

We should probably unify this.
So that we implement this button only once and not for every view individually.

@kolaente commented on 2022-09-26T16:11:44.000Z:

I'd like to have a button to trigger the task wizard from the table view, once that's implemented.

dpschen commented on 2022-09-28T10:20:40.000Z:

I'm still a bit confused between the difference of the task wizard and the quick actions. Shouldn't that be basically the same? So when you can't find any action, select the action to create a new task and then you are in the task wizard.

I see this as similar to in VSCode where (on mac)

  • cmd P triggers 'Go to File' and
    image
  • cmd shift P triggers 'Show all Commands'
    image

Both of them are in the same command menu with the only difference that the latter has > prefixed. When you use the 'Got to File' and write > then you are in the 'Show all Commands' selector. When you delete the > with backspace you end up back in the 'Go to File' selection.

Going back to Vikunjas quick-actions I think we should integrate the task wizard in a similar way: The 'New Task' action there should be the task wizard and not a separate component.

image

So in order to get there we would need to:

  • Create a task wizard integrated in the quick-actions.
  • Create shortcuts that link to the quick-actions with the 'New Task' action preselected.

For the create Task shortcuts I think floating buttons with always the same position could be good. Especially on mobile.

Really cool would be if we could use the speed dial behavior:
Hovering the floating button reveals more actions like new namespace or new list.
But clicking there directly always has 'New Task' as action that opens the quick-actions with the 'New Task' action / task wizard selected. This is a screenshot of a video on that material design page:

image

So in our case it would be in direction from bottom to top something like:

  • New Task (default)
  • New List
  • New Label
  • New Filter
  • New Namespace

@kolaente commented on 2022-09-28T13:42:15.000Z:

So when you can't find any action, select the action to create a new task and then you are in the task wizard.

Going back to Vikunjas quick-actions I think we should integrate the task wizard in a similar way: The 'New Task' action there should be the task wizard and not a separate component.

Yes, but the task wizard can be triggered from other places as well. And it has more options to add task attributes, the create task action only allows quick add magic to add task attributes.
Implementation-wise I think it makes sense to implement the task wizard as a seperate vue component because it is rather complex.

Once the task wizard is implemented it would replace the "new task" action from quick actions.

For the create Task shortcuts I think floating buttons with always the same position could be good. Especially on mobile.

That sounds like a really neat idea.

dpschen commented on 2022-09-28T15:24:30.000Z:

Yes, but the task wizard can be triggered from other places as well.

That's where I took inspiration from the VSCode menu. The 'Show all Commands' (our task wizard) can be opened directly. But you still can go 'back' to the 'Go to File'.

And it has more options to add task attributes, [...]

The other options would be separate components, no? Like the partials in TaskDetailView. So the logic would be abstracted in those. They would only need the current task.

Once the task wizard is implemented it would replace the "new task" action from quick actions.

Sounds like a good idea! :)

dpschen commented on 2022-09-30T12:17:58.000Z:

See also: https://my.vikunja.cloud/tasks/15230

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by PewQuadrat on 2022-07-19T11:01:17.000Z_ Hello, it would be nice if we could also create Tasks from the Table view. In all other list types there is a least a button. Greetings [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1949) --- _**Bouni** commented on 2022-08-17T08:51:44.000Z_: Exactly what I need as well! If I find some spare time, I'll submit a PR for this ... --- _**dpschen** commented on 2022-09-26T13:04:12.000Z_: We should probably unify this. So that we implement this button only once and not for every view individually. --- _**@kolaente** commented on 2022-09-26T16:11:44.000Z_: I'd like to have a button to trigger the task wizard from the table view, once that's implemented. --- _**dpschen** commented on 2022-09-28T10:20:40.000Z_: I'm still a bit confused between the difference of the task wizard and the quick actions. Shouldn't that be basically the same? So when you can't find any action, select the action to create a new task and then you are in the task wizard. I see this as similar to in VSCode where (on mac) - `cmd` `P` triggers 'Go to File' and ![image](/attachments/80d5042b-c847-4881-9517-6db9ac7a9b70) - `cmd` `shift` `P` triggers 'Show all Commands' ![image](/attachments/fa5510f7-bd33-48ce-b154-267b5bec3731) Both of them are in the same command menu with the only difference that the latter has `>` prefixed. When you use the 'Got to File' and write `>` then you are in the 'Show all Commands' selector. When you delete the `>` with backspace you end up back in the 'Go to File' selection. Going back to Vikunjas quick-actions I think we should integrate the task wizard in a similar way: The 'New Task' action there **should be** the task wizard and not a separate component. ![image](/attachments/92cd3e5d-c1a5-45ad-9234-ef32cf116cf7) So in order to get there we would need to: - Create a task wizard integrated in the quick-actions. - Create shortcuts that link to the quick-actions with the 'New Task' action preselected. -------- For the create Task shortcuts I think [floating buttons](https://material.io/components/buttons-floating-action-button) with always the same position could be good. Especially on mobile. Really cool would be if we could use the speed dial behavior: Hovering the floating button reveals more actions like new namespace or new list. But clicking there directly always has 'New Task' as action that opens the quick-actions with the 'New Task' action / task wizard selected. This is a screenshot of a video on that material design page: ![image](/attachments/04ca8b69-e5cc-4b75-ba4f-c90c453eec18) So in our case it would be in direction from bottom to top something like: - New Task (default) - New List - New Label - New Filter - New Namespace --- _**@kolaente** commented on 2022-09-28T13:42:15.000Z_: > So when you can't find any action, select the action to create a new task and then you are in the task wizard. > Going back to Vikunjas quick-actions I think we should integrate the task wizard in a similar way: The 'New Task' action there should be the task wizard and not a separate component. Yes, but the task wizard can be triggered from other places as well. And it has more options to add task attributes, the create task action only allows quick add magic to add task attributes. Implementation-wise I think it makes sense to implement the task wizard as a seperate vue component because it is rather complex. Once the task wizard is implemented it would replace the "new task" action from quick actions. > For the create Task shortcuts I think floating buttons with always the same position could be good. Especially on mobile. That sounds like a really neat idea. --- _**dpschen** commented on 2022-09-28T15:24:30.000Z_: > Yes, but the task wizard can be triggered from other places as well. That's where I took inspiration from the VSCode menu. The 'Show all Commands' (our task wizard) can be opened directly. But you still can go 'back' to the 'Go to File'. > And it has more options to add task attributes, [...] The other options would be separate components, no? Like the partials in TaskDetailView. So the logic would be abstracted in those. They would only need the current task. > Once the task wizard is implemented it would replace the "new task" action from quick actions. Sounds like a good idea! :) --- _**dpschen** commented on 2022-09-30T12:17:58.000Z_: See also: https://my.vikunja.cloud/tasks/15230
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2139
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?