Hey everyone, I’m having a bit of a headache with my GitLab and Jira setup. I’ve got them talking to each other, which is great. When I mention Jira issue numbers in GitLab, it creates the link just fine. But here’s the problem: I can’t get the status changes to work properly.
For some reason, the only status change that’s working is ‘Close’. I’ve tried setting up custom transitions in GitLab with the IDs 11 (To Do), 21 (In Progress), and 31 (Done). But nothing happens when I try to use ‘In Progress’ or any other transition.
I’ve double-checked my Jira setup, and I haven’t touched anything there except for creating an API token. I’m scratching my head trying to figure out what I’m missing. Do I need to tweak something else in Jira or GitLab to get these other transitions working?
Has anyone else run into this issue? Any tips or tricks would be super helpful. I feel like I’m so close to getting this working smoothly! Thanks in advance for any help you can offer!
I encountered a similar challenge when setting up Jira-GitLab integration. One often overlooked aspect is the workflow scheme in Jira. Ensure your project is using a workflow that includes all the desired statuses and transitions. Sometimes, the default workflow doesn’t match custom needs.
Additionally, verify that the Jira user associated with the GitLab integration has the necessary project permissions to execute all transitions. It’s not uncommon for ‘Close’ to work while others fail due to permission discrepancies.
Lastly, check GitLab’s project settings under Integrations > Jira. There’s an option to specify which events trigger Jira updates. Make sure all relevant events (like merge requests and commits) are enabled.
If these steps don’t resolve the issue, consider reaching out to GitLab support. They might have insights into specific configuration nuances affecting transition behaviors.
hey there, i ran into this too. check ur jira workflow - sometimes the transition IDs are diff than u expect. also, make sure ur gitlab user has right permissions in jira.
one thing that fixed it for me was clearing browser cache and restarting gitlab. weird, but it worked!
good luck!
I’ve faced a similar issue with Jira and GitLab integration. The problem often lies in the transition IDs not matching between Jira and GitLab. Here’s what worked for me:
First, double-check the transition IDs in Jira. They might not be 11, 21, and 31 as you’ve set in GitLab. To find the correct IDs, go to your Jira project, click on Project Settings > Workflows > Edit, and hover over the transition arrows. The IDs should appear in the URL.
Once you have the correct IDs, update them in your GitLab configuration. Also, ensure that the user associated with the API token has the necessary permissions to make these transitions in Jira.
Another thing to check is the Jira webhook configuration. Make sure it’s set up correctly to receive updates from GitLab for all transition types, not just ‘Close’.
If all else fails, try regenerating your Jira API token and updating it in GitLab. Sometimes, token permissions can get wonky.
Hope this helps you get those transitions working!