Hey everyone,
I’m having trouble with my GitLab-Jira setup. The basic connection is fine - I can mention Jira issues in GitLab and it creates links. But the status changes aren’t working right.
I set up an API token in Jira and configured GitLab to use custom transitions. My transition IDs are:
11: To Do
21: In Progress
31: Done
The weird thing is, only ‘Close’ actually changes the status in Jira. Everything else just sits there.
I’ve double-checked the GitLab settings. Under Integrations, I turned on Jira transitions and picked ‘Use custom transitions’. But no luck.
Am I missing a step? Do I need to tweak something else in Jira or GitLab to get this working?
Really scratching my head here. Any tips would be awesome!
hey harry, have u checked ur jira webhook settings? sometimes they can b finicky. also, make sure ur gitlab project has the right permissions to update jira issues. i had a similar problem and it turned out i needed to tweak some settings in jira’s application links. good luck!
I encountered a similar issue with Jira-GitLab integration. Have you verified the transition IDs in Jira? Sometimes the workflow’s actual transition IDs don’t match what’s expected, so using Jira’s REST API explorer can help confirm the correct ones.
It’s also worth checking the Jira account permissions linked to your API token. If it only allows the ‘Close’ action, then that might explain why other transitions are failing.
Finally, review your GitLab pipeline configuration to ensure the syntax for triggering the transitions is correct. If all else fails, GitLab support may be able to provide additional troubleshooting insights.
As someone who’s dealt with GitLab-Jira integration headaches, I feel your pain. One thing that’s not immediately obvious is that Jira’s transition IDs can be different for each project, even if the workflow looks the same. I’d suggest double-checking those IDs using the Jira API directly for your specific project.
Another gotcha I ran into was that GitLab needs certain permissions in Jira to make transitions. Make sure your API token has the ‘Browse Projects’ and ‘Transition Issues’ permissions for the relevant project.
Lastly, if you’re using a self-hosted GitLab instance, check if there are any network restrictions preventing it from reaching Jira. I once spent days troubleshooting only to find out it was a firewall issue blocking the outgoing connections.
If none of that helps, diving into GitLab’s logs might give you more clues about what’s going wrong with those non-closing transitions.