Git Integration for Jira (GIJ) Feedback

<1. Summary> I am writing this request following a discussion with the support team regarding the lack of extended character support in the Jira-GitHub integration. (#39014144325) Currently, when creating a Pull Request directly from Jira using the "Create Pull Request" dialog, non-ASCII characters (specifically Korean Hangul) are not encoded correctly. They are transmitted as question marks (??) to GitHub. <2. Steps to Reproduce> 1) Open a Jira issue. 2) Click on "Create Pull Request" in the development panel. 3) In the PR creation dialog, enter a title containing Korean characters (e.g., 한글 테스트). 4) Click "Create". <3. Actual Behavior> The PR is created on GitHub, but the title appears as ?? ??? or garbled text. <4. Expected Behavior> The PR title should properly display the Korean characters (e.g., 한글 테스트) exactly as typed in the Jira dialog. <5. Current Workaround & Pain Point> Currently, I have to create the PR with the broken title in Jira, then navigate to GitHub and manually rename the PR title to Korean. Since GitHub handles Korean characters perfectly when edited directly, this confirms the issue lies specifically within the Jira integration's input handling or API transmission. This double-handling workflow is inefficient for non-English speaking teams. We strongly request adding UTF-8/Extended Character support to the Create PR Dialog to improve usability. Thank you.

In the REST APIs for adding and updating integrations, we have to specify a PAT or username and password. Since GitHub apps are already supported using GitHub Enterprise Server, I want to completely get rid of PATs. It would be nice if we could specify the appId, installationId and privateKey to add a new integration using an existing GitHub app.

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.

We have 1000s of repos sync'd, we'd like to remove those that are not required. Some ability in the UI to search/filter/sort based on last used/commit date, if it has any Jira tickets linked, etc. - the current UI doesn't allow filtering or a way to easily decide we repos can be removed (ie. no commits in years, no linked Jira tickets, etc.) Looking for ways to reduce the number of repos easily (and in bulk) to improve indexing time and take the load off system. We are using app for Jira Cloud connected to ADO

Users (here customers together with us in jira cloud), with are not in development permission (can't see dev panel on work item), are able to browse the app in app menu. By using this option, they are able to access commits with code and messages. Please create to restrict this further access inside the app, using a user group (black or whitelist). We have more than 1000 repositories with around 700+ users.

Hello. We are trying to look at our existing connections and seeing which repos are needed and not. One piece of information which is invaluable to to know the size of each repo in a connection (ideal) and/or the size of the connection as a whole (acceptable) Then we do not have to run a query on our server, which we currently to not host so it makes the ability to do this quite difficult.

Sometimes the reindex feels like it's up and it's hard to tell if it's still running or hung. I would like to have more information about what is happening now. For example, to show the progress of processing commits.

Currently out application does not support project key changes in Jira Cloud. If a Jira project key is changed, our application will not keep the git items that were previously linked using the old Jira issue key. It would be helpful if we could implement support for keeping historical git data links after project key changes.

Add gitTag and gitPullRequest (gitMergeRequest) for JQL queries.

PR create using GitKraken destktop. PR is displayed in gitkraken desktop (pull request source is Azure DevOps) but jira won't show pull request in "Issue activity by GitKraken"