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

Quick Action error when creating a new task #527

New Issue
Closed
opened 2025-11-01 20:58:09 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-01 20:58:09 -05:00
Owner
Copy Link

Originally created by @atomicangel on GitHub (Jun 30, 2025).

Description

When attempting to create a new task using the Quick Action menu, I receive a "No_project" error in the lower left corner.

I do not have any projects besides the default Inbox, if that matters. When I tested this on the demo page, it had a project already created and even after deletion of the project created a task from the Quick Action worked as expected. I then made a project on my instance and the issue still remained, so something to do with the self-hosted variant seems to be the case.

Vikunja Version

Version: v0.24.6

Browser and version

Firefox 139, Fedora Kinoite 42

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @atomicangel on GitHub (Jun 30, 2025). ### Description When attempting to create a new task using the Quick Action menu, I receive a "No_project" error in the lower left corner. I do not have any projects besides the default Inbox, if that matters. When I tested this on the demo page, it had a project already created and even after deletion of the project created a task from the Quick Action worked as expected. I then made a project on my instance and the issue still remained, so something to do with the self-hosted variant seems to be the case. ### Vikunja Version Version: v0.24.6 ### Browser and version Firefox 139, Fedora Kinoite 42 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 20:58:10 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 30, 2025):

This should go away if you set the inbox project as the default project in the user settings. Does that work for you?

There have been a few issues around this, all of which should be fixed but not yet released (that's why it works on the demo)

@kolaente commented on GitHub (Jun 30, 2025): This should go away if you set the inbox project as the default project in the user settings. Does that work for you? There have been a few issues around this, all of which should be fixed but not yet released (that's why it works on the demo)
GiteaMirror commented 2025-11-01 20:58:10 -05:00
Author
Owner
Copy Link

@atomicangel commented on GitHub (Jul 1, 2025):

I had Inbox set as my default project from the beginning but just to be on the safe side I double checked and confirmed. Verified the behavior is still occurring.

@atomicangel commented on GitHub (Jul 1, 2025): I had Inbox set as my default project from the beginning but just to be on the safe side I double checked and confirmed. Verified the behavior is still occurring.
GiteaMirror commented 2025-11-01 20:58:10 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 1, 2025):

Can you verify if this works with an unstable build?

@kolaente commented on GitHub (Jul 1, 2025): Can you verify if this works with an unstable build?
GiteaMirror commented 2025-11-01 20:58:10 -05:00
Author
Owner
Copy Link

@atomicangel commented on GitHub (Jul 17, 2025):

I apologize, I haven't had the time to check into this. I am running the docker version, and when I change my docker compose to vikunja/unstable or vikunja/latest I am getting access denied or repo does not exist.

@atomicangel commented on GitHub (Jul 17, 2025): I apologize, I haven't had the time to check into this. I am running the docker version, and when I change my docker compose to vikunja/unstable or vikunja/latest I am getting access denied or repo does not exist.
GiteaMirror commented 2025-11-01 20:58:11 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jul 17, 2025):

The docker image has a tag of unstable, it's not a separate image. The full image would be vikunja/vikunja:unstable.

@kolaente commented on GitHub (Jul 17, 2025): The docker image has a tag of unstable, it's not a separate image. The full image would be `vikunja/vikunja:unstable`.
GiteaMirror commented 2025-11-01 20:58:11 -05:00
Author
Owner
Copy Link

@atomicangel commented on GitHub (Jul 21, 2025):

Confirmed that unstable is working as expected.

@atomicangel commented on GitHub (Jul 21, 2025): Confirmed that unstable is working as expected.
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#527
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?