This formats references to YouTrack issues in commit messages as links to the target issues in YouTrack. The first thing you should do is enable the YouTrack integration in GitLab. For instructions, see SSL Certificates.Įnable the YouTrack Integration in GitLab
For security, use this option only when both YouTrack and your GitLab server run on a private computer network. If the certificate for your server is self-signed, you need to import the certificate and public key to establish a secure connection. You should be able to connect to the server without importing its SSL certificate. If your GitLab server has a valid certificate that is signed by a well-known certificate authority (CA), the JVM vendor may have already added the root (CA) certificate to the certificate store. If you're integrating with a GitLab CE or GitLab EE installation and want to establish a secure (HTTPS) connection with the server, you may need to import the SSL certificate for your GitLab server into YouTrack. You can either use an account that has at least Master or Owner access level in the project or a GitLab administrator account. This is the user account whose private access token is used for authentication. The account that you use to connect to GitLab has access to the GitLab project that you want to manage with this integration. Specifically, you need to make sure that your network doesn't block connections between your VCS server and YouTrack. YouTrack is accessible to inbound connections. For more information, see Integrate with GitLab.Īs an administrator, you can enable the GitLab integration for any project in YouTrack. This operation can also be performed by a project administrator on a per-project basis. When you enable and configure the GitLab integration, you define mappings between a YouTrack project and a GitLab repository. For more information, see Link Issues in VCS Commits. For details, see Pull Requests.Īdd links to YouTrack issues in commit messages or branch names. For more information, see Commits.ĭisplay the status of pull (merge) requests directly in the activity stream of any issue that is referenced in the title or description of the pull request. Track commits that are related to specific issues in the activity stream for each issue. For more information, see Apply Commands in VCS Commits. (If you are reporting a bug on, write: This bug happens on GitLab.Follow the instructions on this page to integrate with VCS repositories that are hosted on, self-hosted GitLab Community Edition (CE), or self-hosted GitLab Enterprise Edition (EE) server.Ī GitLab integration enables the following features in YouTrack:Īpply commands to YouTrack issues in commit messages.
#GITLAB YOUTRACK INTEGRATION CODE#
Logs, and code as it's tough to read otherwise.) Output of checks (Paste any relevant logs - please use code blocks (```) to format console output, Issues ids starting with a lowercase letter should be matched by the Youtrack integration. Issues ids starting with a lowercase letter aren't matched by the Youtrack integration. Steps to reproduce Example Project What is the current bug behavior? This was initially introduced in #42595 (closed). This isn't a real requirement by Youtrack as we have a lot of project which start with a lowercase letter. The Youtrack integration requires issues to start with a capital letter ->
0 kommentar(er)
