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

[FR] Option to add subtask from within task details pannel #1761

New Issue
Closed
opened 2026-03-22 13:35:16 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-03-22 13:35:16 -05:00
Owner
Copy Link

Originally created by @RoboMagus on GitHub (Mar 10, 2022).

Currently it seems to be only possible to add a 'subtask' relation for existing tasks using the 'add task relations' option.
However it would be a great improvement to be able to add such a subtask from the same menu as well, if a task with the provided name does not already exist.

Originally created by @RoboMagus on GitHub (Mar 10, 2022). Currently it seems to be only possible to add a 'subtask' relation for existing tasks using the 'add task relations' option. However it would be a great improvement to be able to add such a subtask from the same menu as well, if a task with the provided name does not already exist.
GiteaMirror commented 2026-03-22 13:35:17 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 10, 2022):

That already works. What version are you using? Can you reproduce this on try?

@kolaente commented on GitHub (Mar 10, 2022): That already works. What version are you using? Can you reproduce this on [try](https://try.vikunja.io)?
GiteaMirror commented 2026-03-22 13:35:19 -05:00
Author
Owner
Copy Link

@RoboMagus commented on GitHub (Mar 11, 2022):

Ah, yes. I see the problem now.

I am using the latest greatest versions for all Vikunja containers, and I could reproduce this in try.
The scenario that I ran into was typing the name of the Subtask and then hitting the button add a new task relation, which would then throw me an error cannot read properties of null (reading 'id').
After trying some variations on this, when just hitting enter after filling in the subtask name it works as intended.

I expected the on screen button and enter to perform the same action though. Is that not the case?

@RoboMagus commented on GitHub (Mar 11, 2022): Ah, yes. I see the problem now. I am using the latest greatest versions for all Vikunja containers, and I could reproduce this in `try`. The scenario that I ran into was typing the name of the Subtask and then hitting the button `add a new task relation`, which would then throw me an error `cannot read properties of null (reading 'id')`. After trying some variations on this, when just hitting `enter` after filling in the subtask name it works as intended. I expected the on screen button and enter to perform the same action though. Is that not the case?
GiteaMirror commented 2026-03-22 13:35:20 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 22, 2022):

Interesting, I was not able to reproduce the error about the missing property - I got an error the task would not exist (which kind of makes sense, given that Vikunja didn't create it on the fly).

Can you provide exact steps to reproduce the bug?

How should this work? The same when pressing enter and clicking "Add a new task relation"?

@kolaente commented on GitHub (Mar 22, 2022): Interesting, I was not able to reproduce the error about the missing property - I got an error the task would not exist (which kind of makes sense, given that Vikunja didn't create it on the fly). Can you provide exact steps to reproduce the bug? How should this work? The same when pressing enter and clicking "Add a new task relation"?
GiteaMirror commented 2026-03-22 13:35:21 -05:00
Author
Owner
Copy Link

@RoboMagus commented on GitHub (Mar 28, 2022):

When trying to reproduce now I no longer get the same error message. This may have changed when I've updated the vikunja docker images.

For the record, what I would do is:

  1. Open an existing task in the kanban board
  2. From the sidebar select add task relations
  3. Enter a subtask title in the textbox.
  4. Select subtask from the dropdown list.
  5. Click Add a new task relation.

When going through the same steps now I get Request failed with status code 404. The list task does not exist.

To avoid user confusion, would it be possible to create the task when clicking the button when a task with the provided name does not exist?

@RoboMagus commented on GitHub (Mar 28, 2022): When trying to reproduce now I no longer get the same error message. This may have changed when I've updated the vikunja docker images. For the record, what I would do is: 1. Open an existing task in the kanban board 2. From the sidebar select `add task relations` 3. Enter a subtask title in the textbox. 4. Select `subtask` from the dropdown list. 5. Click `Add a new task relation`. When going through the same steps now I get `Request failed with status code 404. The list task does not exist.` To avoid user confusion, would it be possible to create the task when clicking the button when a task with the provided name does not exist?
GiteaMirror commented 2026-03-22 13:35:21 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 30, 2022):

To avoid user confusion, would it be possible to create the task when clicking the button when a task with the provided name does not exist?

I think that would be the best solution, yes.

@kolaente commented on GitHub (Mar 30, 2022): > To avoid user confusion, would it be possible to create the task when clicking the button when a task with the provided name does not exist? I think that would be the best solution, yes.
GiteaMirror commented 2026-03-22 13:35:21 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Apr 2, 2022):

Should be fixed in dfed1f438a - please verify with the next unstable release in ~30 min if the fix works for you.

@kolaente commented on GitHub (Apr 2, 2022): Should be fixed in dfed1f438a168606617d2ecef55cd83ff724201f - please verify with the next unstable release in ~30 min if the fix works for you.
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#1761
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?