Atlassian GitLab for Jira app (for GitLab Self-managed) gaps and support

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

During the process of developing the GitLab for Jira app for GitLab Self-managed, we've come across a few gaps and/or questions which may need Atlassian support:

1. Creating a GitLab branch from a Jira issue

We have a feature that allows to create a branch from Jira. This is basically a link on Jira that points to a page on gitlab.com. The link looks like this:

https://gitlab.com/-/jira_connect/branches/new?issue_key={issue.key}&issue_summary={issue.summary}

Issue key and issue summary, are the only parameters we receive from Jira (see the property definition here). There appears to be no way for us to link the request to an installation and therefore to a self-managed instance.

2. It's not clear if the app supports creating commits and MRs from Jira - no documentation was found on this

3. Using Jira toolchain to link projects - The toolchain feature described in #378623 (closed) is not controlled by the GitLab for Jira app even though the UI makes it look like it is. We probably won't be able to add self-managed support to it without being able to modify it.

4. When creating a branch, similar to point #2, we are unable to filter out irrelevant namespaces - We have an existing issue describing this problem, which appears to also depend on retrieving a token from the create branch link. From my engineering team: "The create branch link still doesn't provide a token that we can use to identify the installation, and the development action still only supports issue key and summary as parameter."