Git Integration for Jira (GIJ) Feedback

Our environment forces us to connect to individual repositories, and we have a large number of these connections which synchronize frequently. This causes gitkraken to write a very large number of messages to Jira's audit log, making it difficult to notice/find messages caused elsewhere. It would be very helpful to have a plugin admin setting to turn off output to the audit log.

We run a self-managed Jira Data Center and have purchased the GitKraken Git/Jira integration app. We set up our integrations individually using "Add New Integration". We would like to see Merge Requests on the Jira Development Panel, but that functionality does not exist, confirmed by the response to ticket #2587033419. Our user base has a strong interest in having this feature available.

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.

Today, when creating feature GitHub JIRA via JIRA issue, the field of "Repository" shows the first repository in ABC order. We want that it will show the last repositories that the user created with them branched in the last times. The support team told me that feature is already appear in the JIRA cloud version, but on the JIRA Data Center it doesn't appear. Please see the attached screenshot.

The component function is required.

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.

With time as PR/MR are merged to the main/developed branch, tags become associated to the main branch. This will eventually show multiple tags for different branches when they are merged. Allow the user to specify the number of tags that should be displayed in the issue view.

Allow the user to select which PR/MR status will be visible. For instance if PR/MRs are closed, they could be hidden. Also provide a way to view the excluded status/es in the particular issue if desired.

Hello there, we are hitting rate limits with AWS Code Commit Pull Requests (5 request per second), this is because the details of the Pull Requests attached to a repository are not being filtered by pullRequestStatus. A PR in Code Commit can have a status of open or closed, you cannot delete them, so the integration is making hundreds of requests for historical PR's. Can we have an option for a filter for the Code Commit PR's to pullRequestStatus of OPEN only, https://docs.aws.amazon.com/codecommit/latest/APIReference/API_ListPullRequests.html#API_ListPullRequests_RequestSyntax Another option is only request PR information with pullRequestStatus of OPEN when triggered by a webhook with a repo specified?

Implement a smart approach for handling Atlassian Jira Dev Info rate limit exceptions (429). Allow for smart reprocessing after the limit has been reached.