Resolve "Jira Connect integration fails for branches with slashes"
What does this MR do?
Change the branch ID we send to Jira so that it doesn't throw an error when there are special characters.
We use a SHA256 hash of the branch name so that it's still unique per branch name while being alphanumeric.
The ID is used by Jira to determine uniqueness of the branch so that it knows whether to add / update this dev info. It is not used for display in the UI.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Markus Koller