Git Integration for Jira (GIJ) Feedback

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.

We have standardised branch naming guidelines, and one request from a stakeholder was having the ability to restrict the branch creation template such that you cannot create a branch without a jira Issue Key, since it currently allows a user to modify the template in any capacity that they like. This way, it would allow us to establish and enforce the standards.

Once a Issue is resolved, we would like the ability to disable the ability to create a new branch from said Jira Issue. This is to prevent branches being associated with issues that are considered "done" by the business

For users whose Jira is hosted behind a firewall/proxy, and they are unable to expose the internal URL, Github apps will get stuck in 'Installing' status due to the installation completion webhooks not reaching the intended internal (private) endpoint. As a work around, some clients have been able to successfully setup external facing proxy URL's to capture the webhooks and forward them to the correct internal endpoint to complete the installation. In this workflow, the webhook URL from the Github App must be retrieved on the GH side of things after the app has been authenticated, then the proxy is configured to redirect to this (original) internal endpoint. Once that is done, the GH app webhook must be modified to point to the proxy URL, and then the webhooks must be resent to complete the installation. For clients like these, it would be extremely helpful to have an advanced settings field that would allow them to specify a different proxy URL domain, which will be passed in the GH App manifest instead of the internal domain. This way, the clients will not have to manually go and grab the webhook URL and then point the proxy to the original URL. The Proxy can be setup to route the external domain URLs to the internal domain endpoints. In the proposed workflow, the GH app will be created with the proxy URL, and the webhooks should be delivered to the to the internal address without any manual modifications to anything.

Currently, the plugin only supports Classic Release pipelines. While these are great for most use cases, some customers do use the power of yaml pipelines were they can define multiple stages and steps.

Gitea is one of the few self-hosted opensource platforms around, yet Git's integration with Jira lacks the most useful features you find with other platforms (branching, triggers, etc). It'll be really handy to have those features available for Gitea as well.

Customers have requested that Git Integration for Jira support webhook indexing for Gitea as it supports webhooks natively.

Add enabling / disabling options (branch creation, merge creation and showing of Git issue panel) per issue type. Some customers have specific issue types that should not provide the ability to create branches and pull requests.

In GIJ Cloud, when inside of "Settings for Integration" in the "Choose repositories" menu, there's no easier way to navigate between the pages besides the buttons "Prev" and "Next", which can be bothersome when having a lot repositories in the integration. Please provide a easier navigation, e.g., letting the user select to which page they want to go.

In GIJ Cloud, when inside of "Settings for Integration" in the "Choose repositories" menu, if there are 3 repositories, the last one is never visible. Please provide a fix for this issue to improve the user's experience when selecting the integrations' repositories.