Jira integration: Password cannot be blank error when switching to default settings
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
A large Premium, Self-Managed customer reported the following issue with being unable to switch from custom to default settings for JIRA.
Steps to Reproduce
Here is a recording of the customer detailing and demonstrating the steps to reproduce the issue. (GitLab internal only)
Note that this only occurs on the group level.
What is the current bug behavior?
Password cannot be blank error.
What is the expected correct behavior?
When switching from "custom settings" to "default settings" Gitlab should not flag a missing JIRA credential as an error. Users shouldn't be prompted for a password because it's authenticated at the instance level.
Most project maintainers don't know the JIRA credentials. Having the JIRA credentials in a central location is one of the use cases for using the "default settings".