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

Unable to open a feature request without leaving Github platform #97

New Issue
Closed
opened 2025-11-01 20:46:50 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 20:46:50 -05:00
Owner
Copy Link

Originally created by @RoboMagus on GitHub (Oct 18, 2022).

Description

Since the beginning of this month it seems to be impossible to open any new issue for the Vikunja Frontend other than bug reports.

Though I get the use of a community forum to open up discussions, making it the only place to request for new features requires Github users to register to yet another platform, which at least for me makes the process too cumbersome.
Especially since there was a perfectly usable way of creating feature requests using the Github issue templates.

Vikunja Frontend Version

Latest

Vikunja API Version

Latest

Browser and version

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @RoboMagus on GitHub (Oct 18, 2022). ### Description Since the beginning of this month it seems to be impossible to open any new issue for the Vikunja Frontend other than bug reports. Though I get the use of a community forum to open up discussions, making it the only place to request for new features requires Github users to register to yet another platform, which at least for me makes the process too cumbersome. Especially since there was a perfectly usable way of creating feature requests using the Github issue templates. ### Vikunja Frontend Version Latest ### Vikunja API Version Latest ### Browser and version - ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2025-11-01 20:46:51 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 20, 2022):

I've disabled that because there are too many places where users could request features. This duplicated the conversations across GitHub, Gitea and the forum. While we usually link issues or discussions for each feature request to the relevant backlog items, enabling creating new issues led to discussing the same things multiple times.

I understand that it creates friction but given that GitHub is not the primary development platform used for Vikunja I'd say it makes more sense like that. To ease the transition a bit I've just enabled login with GitHub in the forum.

@kolaente commented on GitHub (Oct 20, 2022): I've disabled that because there are too many places where users could request features. This duplicated the conversations across GitHub, Gitea and the forum. While we usually link issues or discussions for each feature request to the relevant backlog items, enabling creating new issues led to discussing the same things multiple times. I understand that it creates friction but given that GitHub is not the primary development platform used for Vikunja I'd say it makes more sense like that. To ease the transition a bit I've just enabled login with GitHub in the forum.
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#97
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?