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

GitLab issue sync #429

New Issue
Open
opened 2025-11-01 20:56:06 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-01 20:56:06 -05:00
Owner
Copy Link

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

Original issue by alexanderadam on 2023-02-17T19:50:29.000Z

It would be great to have a card be automatically created when an issue is created on a GitLab repo; and conversely, a GitLab issue be created when we create a card in Vikunja.

PS: Thank you for working on Vikunja!

Original issue on Gitea

@kolaente commented on 2023-02-19T19:47:18.000Z:

I like the idea to have something like this (maybe for GitHub as well), but I wouldn't build it into Vikunja itself. Similar to SyncLinear.

white-gecko commented on 2023-05-02T14:29:17.000Z:

Actually, just after entering the webpage reading the header:

image

"Organize everything, on all platforms."

Also the section:

"Import your tasks from Todoist, Trello or Microsoft To-Do

Because work does not happen in one tool only."

underpinned that somehow.

My first thought was, that the aim of vikunja actually is to provide a common interface to manage all todos on all other platforms (like gitlab, github, confluence, multiple gittea instances, trello, maybe any CalDAV VTODO interface, …), just in one place.

This could also be a generalized feature of the migration feature (https://try.vikunja.io/migrate)

If you say "but I wouldn't build it into Vikunja itself", you would see it as an extra service translating the relevant apis to the vikunja API, is that right?

@kolaente commented on 2023-05-02T15:40:12.000Z:

If you say "but I wouldn't build it into Vikunja itself", you would see it as an extra service translating the relevant apis to the vikunja API, is that right?

Rather something which pulls the other service's API and pushes it into Vikunja's.

alexanderadam commented on 2023-08-17T12:32:53.000Z:

Not sure whether this makes any difference here but people using Focalboard for now are looking for this too and since Focalboard is not getting any new features unless the community is really taking over, Vikunja might be a very viable alternative to change to.

Hence these people might look for this feature here, too.

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by alexanderadam on 2023-02-17T19:50:29.000Z_ It would be great to have a card be automatically created when an issue is created on a GitLab repo; and conversely, a GitLab issue be created when we create a card in Vikunja. - It should allow to use self hosted instances - [GitLab's Issues API is well documented](https://docs.gitlab.com/ee/api/issues.html) - [Developers can reference issues in their commits](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) and if a corresponding GitLab issue would be closed, the twin issue in Focalboard could be automatically closed as well **PS:** Thank you for working on Vikunja! [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/1397) --- _**@kolaente** commented on 2023-02-19T19:47:18.000Z_: I like the idea to have something like this (maybe for GitHub as well), but I wouldn't build it into Vikunja itself. Similar to [SyncLinear](https://synclinear.com/). --- _**white-gecko** commented on 2023-05-02T14:29:17.000Z_: Actually, just after entering the webpage reading the header: ![image](/attachments/a3f56afe-86f3-4c57-b180-e880799034d6) "Organize everything, on all platforms." Also the section: "Import your tasks from Todoist, Trello or Microsoft To-Do Because work does not happen in one tool only." underpinned that somehow. My first thought was, that the aim of vikunja actually is to provide a common interface to manage all todos on all other platforms (like gitlab, github, confluence, multiple gittea instances, trello, maybe any CalDAV VTODO interface, …), just in one place. This could also be a generalized feature of the migration feature (https://try.vikunja.io/migrate) If you say "but I wouldn't build it into Vikunja itself", you would see it as an extra service translating the relevant apis to the vikunja API, is that right? --- _**@kolaente** commented on 2023-05-02T15:40:12.000Z_: > If you say "but I wouldn't build it into Vikunja itself", you would see it as an extra service translating the relevant apis to the vikunja API, is that right? Rather something which pulls the other service's API and pushes it into Vikunja's. --- _**alexanderadam** commented on 2023-08-17T12:32:53.000Z_: Not sure whether this makes any difference here but [people using Focalboard for now are looking for this too](https://github.com/mattermost/focalboard/issues/2597) and since [Focalboard is not getting any new features unless the community is _really_ taking over](https://github.com/mattermost/focalboard/commit/615b6ceee7d490d2988d93d3b7facd4f7f48aa48), Vikunja might be a very viable alternative to change to. Hence these people might look for this feature here, too.
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#429
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?