Jira Integration: Custom Configurations Don't Inherit Credentials From Parent Level
Summary
When updating Jira integration credentials at the organization/group level, subgroups and projects with custom Jira configurations cannot inherit the new credentials. Switching these custom integrations to "use default settings" results in authentication errors, forcing users to either lose all customizations or manually update credentials at every level.
Related Issues:
Steps to reproduce
- Configure Jira integration at the organization/top-level group with credentials.
- At a subgroup or project level, create a custom Jira integration configuration (e.g., enable/disable specific features like commits, branches, etc.)
- Change the Jira instance (e.g., migrate from self-managed to SaaS with new URL).
- Update the organization/top-level Jira integration with new credentials.
- Test connection at top level - it works successfully.
- Navigate to a subgroup/project with custom Jira configuration.
- Attempt to switch from "Use custom settings" to "Use default settings" to inherit new credentials.
- This will likely cause authentication failure.
What is the current bug behaviour?
- When attempting to switch a custom Jira integration to use default settings, the form displays:
Password can't be blank. - Testing the connection returns:
Connection failed. Check your integration settings. unexpected character: 'Client' at line 1 column 1. - The only way to get new credentials working at lower levels is to completely revert to default settings, which loses all team customizations.
What is the expected correct behaviour?
Authentication credentials (URL, username/token, password) should be inherited.
Switching from custom to default settings should successfully inherit the updated credentials without errors.
Output of checks
This bug happens on GitLab.com.
Possible fixes
Allow credentials to be inheritable from parent.
Allow customization at lower levels (feature toggles, custom fields).
Edited by Alexandria Balkaran