Gitlab - changing diacritical to base characters as an option
under review
C
Cezary Janiak
When creating branch/MR it takes task name, but it can contain letters other than base (diacritical). They're cut out and target name is ugly then. Option when creating task would be nice (or in integration options)
Now it has to be done manually - it takes time and focus
Log In
Tadej Jevševar
under review
Tadej Jevševar
Thanks for the feedback! At the moment, our GitLab integration requires an exact match for task IDs, including any diacritical characters.
We don’t currently normalize characters like "č" → "c", but we’re curious: is the main issue with GitLab branch naming, commit parsing, or CI tools misreading the task ID? Would an optional toggle to strip accents before embedding the task ID in branch names solve the problem for your team?
Understanding your flow will help us explore whether this belongs in the ClickUp side of the integration or if there’s a GitLab-side workaround.
C
Cezary Janiak
Tadej Jevševar problem is with both branch naming - but that's fully understandable to strip off other characters than base english. And then with MR naming - here it shouldn't be such as problem
Our PM creates a branch from task view -> characters are stripped
Then creates a MR from that branch -> so again diacritical characters are missing
We tried to add polish characters to both during creation: and both actions then were forbidden in clickup
Meanwhile (attachement) creating for example issue in gitlab from mail works fine with all characters we need
Optional toggle for normalizing characters from task name would be fine for us
Tadej Jevševar
Thanks, Cezary Janiak: — that’s super clear.
Got it: your team creates branches and MRs directly from task view, but diacritical characters are stripped during both actions — and adding them manually isn’t allowed either. Appreciate the example — that’s helpful.
We’ll explore adding a toggle to normalize characters (e.g. “ć” → “c”) or preserve them where possible, especially for MR names where stricter naming isn’t needed. Will follow up here as we dig into implementation options!