Git Integration for Jira (GIJ) Feedback

Add support for GitHub Enterprise Cloud repositories with Data Residency. By their nature these repositories use a different endpoint which is not currently supported by Git Integration for Jira.

Currently, when enabling the Git Service Permissions enforcement option, Gerrit and Single Git / SSH integrations disappear. This is because the plugin will favor the permission enforcement. Grant both settings for integrations that do not support the Git Service Permission layer.

Endoka House for Advanced Science and Technology

GIJ DC currently offers the 'Enforce Git Service Permissions' setting, which helps clients restrict data visibility to only the things that their user account has access to. This would be a great addition to GIJ Cloud in order to have more security options available to users looking to restrict data visibility.

The create branch / pull request dialog, limits the repository drop-down to ten elements. This is to maximize performance. When a user search for a repository, sometimes, the names are related to organizations/groups and this makes difficult to identify the specific repository. Allow users to specify the number of listed repositories in the search box.

We have a request from some developers working in Gitlab self-hosted, regarding smart commits. Where they have the possibility to include multiple Jira tickets in the same commit. The default way that commit message then gets linked to one or multiple Jira tickets. Our feature request is that on a specific repository in the Gitkraken "manage repositories" as an advanced option to include a "regex" and/or a settings to only fetch the first valid Jira ticket. An example of a commit: Did a change solving "TEST-123" this is also to be worked on in ticket "ABC-123". What we would then mean is that, Gitkraken would only link the commit to "TEST-123" and ignore the last Jira ticket number "ABC-123". So basically a way to "aim" the Smart Commit to one Jira-ticket even if it has multiple Jira-ticket-references.

We have a request from some developers working in Gitlab self-hosted, for some repositories there is a need to ignore linking the commits towards a Jira ticket. For Gitkraken to only fetch the information from a repository when there is a merge-request. Our feature request is that on a specific repository in the Gitkraken "manage repositories" as an advanced option to include a setting to only fetch the the commit that's part of a merge request. An example would be that a developer is doing many commits related to a Jira ticket "TEST-123" but its first when he/she do a merge-request commit that its gets linked to the "TEST-123" ticket. It would mean that only the merge request commit would be highlighted in the Jira ticket. Not the before non merge-request commits.

we are using now jira cloud with git plugin. On our server jira was no group for each repository, so we don't care to split our project in different parts at Bitbucket. But now we see every part as separate repository and every repository as a group in git commit view. That's why we want to add the possability to "not group" by repository.

Similar to the Branch name template, provide an option to modify the description message used for when the pull requests are created with the Git Integration for Jira add-on.

Often times, users need to know the name of the integration for specific repositories. Create a toggle option to allow integration name display as a column in the repository browser.