GitLab issue sync #1397

Open
opened 2023-02-17 19:50:29 +00:00 by alexanderadam · 4 comments

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!

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!
Owner

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.

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/).

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?

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?
Owner

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.

> 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.
Author

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.

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 Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#1397
No description provided.