Gitlab V2
complete
S
Shelton
Long list of integration improvements I would love to see.
- Associate a Repo with a Project
- Thus, all GL issues have a 1-1 relationship with a task.
- Comments (and actions) made on one service are pushed to the other; each direction optional.
- Tag sync
- Option to disassociate Repo with Space. For the current alignment to work I need a Space for each Repo. Doesn't make sense to me ... unless I'm using clickup incorrectly.
- Option to create a subtask when a merge request is created for an associated user.
Log In
m
maydanw
Could you pease add a link on this thread (or somewhere else) where can I find a manual how to load into Clickup all of my existing GL issues?
Thanks
Rey Tugade Jr
Am I missing something? My bad but I can't seem to find the functionality where I can manage (create, update, delete) issues directly from the ClickUp interface. Is this something possible with the current integration?
W
Will Adams
Rey Tugade Jr: yeah same issue here, i just want to even be able to view the gitlab issues on clickup, so a PM doesn't have to log into gitlab to see the issues, also don't want to create duplicate issues in clickup for every issue in gitlab and have to link the two, but i can't seem to access gitlab issues from clickup
Sergio
Thanks for the latest update, it looks great! I find very useful the ability to create branches and merge requests directly from the Clickup tasks, but it is a bummer that only admins can do it.
I spoke with support and they suggested to leave a comment here. Am I missing something? Regular users should be able to create their own branches since they are also allowed to do so from Gitlab directly.
Thanks
Nick Krekow
Sergio: Hey Sergio! This will be fixed this week! This is a bug and it has to do with the fact we support self hosted versions of Gitlab in addition to the cloud version.
Ł
Łukasz Chlebowski
Nick Krekow: IMO fields could have default values like repo, source/target branch. Adding repos to list instead space will be great and will help keep things clean.
And another suggestion: GL could generate links to CU in commit/merge request messages but task id must be numeric
Sergio
Nick Krekow: Hey Nick, thanks for the quick reply! Looking forward to the next release
Ivan Villa
complete
S
Sophia Kaminski
From enterprise client support ticket: Is it possible to have a tighter coupling of clickup tasks with gitlab issues? Gitlab issues have tags and a board like clickup does. It would be great if clickup could reflect it's changes to gitlab. More specifically:
- CU lists should be tied to gitlab repositories
- creating a CU task in a specific list should create an issue in the linked repository
- opening an GL issue in a linked repo should create a CU task in the connected list
- changing the status of a CU task e.g TODO -> Doing, should change the tag of the gitlab issue
- a specific CU status should close a GL task
- closing a GL task should change the status of the CU task
- tags on the CU task should be reflected in the gitlab issue
A
Aries Sanchez Sulit
Sophia Kaminski: How's the update with this? that's what I'd like to have too, the GitLab issues board is heavily tied on a ClickUp project so that each ClickUp cards can be represented as a branch (with out manually linking) and updates the status with using the existing CU command.
L
Linden Dale-Gandar
Sophia Kaminski: This is marked as complete, but as far as I can tell most of these changes were not included. Unless I'm missing something none of the items below about linking Gitlab Issues and Clickup tasks were implemented?
- creating a CU task in a specific list should create an issue in the linked repository
- opening an GL issue in a linked repo should create a CU task in the connected list
- changing the status of a CU task e.g TODO -> Doing, should change the tag of the gitlab issue
- a specific CU status should close a GL task
closing a GL task should change the status of the CU task
S
Sophia Kaminski
From support ticket: I would to like to reference ClickUp ID’s within GitLab Comments so that they automatically appear within the related Clickup issue
Robert Clancy
I find the current gitlab integration very poor. And the zappier one too so I can't do things with it. I would like to simply have merge requests open in clickup, but on zapier you have to set a list and I don't want to update zapier for every sprint to change the list to the current one.
Going to add the things that we need to make the integration useful for our workflow:
- better way to copy the ID of a task for a commit message, the ID should be part of the UI without needing a click or hover, it's important for a lot of things not just commit messages
- merge requests to create new tasks
- commits in gitlab with task ID to link to clickup
- triggers from statuses, EG: move task from [in-progress] to [in-review] to automatically create a merge request or just make a sub task saying someone needs to make one and link it
- make it so when you associate commits/branches with a task it isn't hidden as tiny (collapsed sometimes) activity and a number alert over the gitlab log. actually have that information in the task to view it in the list and card so it is useful and not just some thing off to the side you need to really look for
- hell the entire modal with gitlab information should just be part of the card and then this integration is instantly more useful
I guess I want a far deeper integration and it just won't happen. But if zappier was more than very minimal options I could do a lot of this stuff myself.
R
Roisin Russell
Agree- ClickUp can jump in and try to fill the void left when Waffle dies in next few months.