Git Integration for Jira (GIJ) Feedback

We have several small repositories for a single jira project, but it is only possible to choose a default on project level. It would be cool if it was also possible to make a default for every Components in a project

The option to receive a notification in Jira or via email when a repository synchronization fails would be beneficial. A notification when a repository indexing fails would also be very useful.

Add support for Azure DevOps Multi-Tenant Org connection through OAuth. Currently the plugin connects to the Home Tenant of the user provided through OAuth. In some cases users were shared access to other tenant organizations, but these are not listed in the connection. Review GITCL-1553

migration: Is Cloud-to-Cloud migration supported? Is there any migration utility or API available? What data will NOT be migrated during the process? Are there any Cloud feature limitations that we should be aware of? Is professional services support recommended or required for the migration? Additionally, please let us know if there are any specific steps or prerequisites required for: Jira projects Users and groups Workflows, permission schemes, and configurations Automations and integrations Marketplace apps and app data migration Your guidance on the overall migration process, prerequisites, and best practices would be very helpful for our planning and execution.

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.

Customer requested to change the main Git Integration for Jira caption "Issue Activity by GitKraken" to Development Information.

Customer requested to change the main Git Integration for Jira to Development Information.

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.

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.

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.