Minor version update

v4.23.1

• New Feature: Added the ability to cancel the indexing of a repository, which can be performed from the Indexing Queue page. Indexed data will remain at the point it was cancelled and the repository will have a status of Canceled.
• Improved the performance of indexing repositories with a large number of branches. This will be most noticeable with repositories that contain 100+ branches.
• Improved the performance of indexing nested repositories for Gerrit users.

v4.23.1

• New Feature: Added the ability to cancel the indexing of a repository, which can be performed from the Indexing Queue page. Indexed data will remain at the point it was cancelled and the repository will have a status of Canceled.
• Improved the performance of indexing repositories with a large number of branches. This will be most noticeable with repositories that contain 100+ branches.
• Improved the performance of indexing nested repositories for Gerrit users.

v4.22

• Corrected an issue that was causing a blank dialog box in the Repository Browser when requiring user PATs for AWS integrations.
• Corrected an issue that was causing Smart Commit error emails to be sent when "Send commit notification emails" was not enabled.
• Corrected a Smart Commit documentation link contained within Smart Commit error emails.

v4.22

• Corrected an issue that was causing a blank dialog box in the Repository Browser when requiring user PATs for AWS integrations.
• Corrected an issue that was causing Smart Commit error emails to be sent when "Send commit notification emails" was not enabled.
• Corrected a Smart Commit documentation link contained within Smart Commit error emails.

v4.21

• Corrected a bug that was preventing the "Advanced" drop-down menu on Integration Connection Settings from opening.
• Modified Git Integration for Jira and GitKraken logos, fonts, and colors to reflect updated branding.

v4.21

• Corrected a bug that was preventing the "Advanced" drop-down menu on Integration Connection Settings from opening.
• Modified Git Integration for Jira and GitKraken logos, fonts, and colors to reflect updated branding.

v4.20

• Improved reindex performance when Git Service Permissions mode is enabled and there are nested repositories that cannot be cloned (was previously causing the application to recalculate permissions).
• Optimized performance of Indexing Queue Viewer
• Added the ability to log Gerrit GetRepositories response in atlassian-jira.log by turning on DEBUG logging

v4.20

• Improved reindex performance when Git Service Permissions mode is enabled and there are nested repositories that cannot be cloned (was previously causing the application to recalculate permissions).
• Optimized performance of Indexing Queue Viewer
• Added the ability to log Gerrit GetRepositories response in atlassian-jira.log by turning on DEBUG logging

v4.19.1

Feature Improvement:

• Added a pull request filter to the Integration Features Settings page. This allows Admins to hide pull requests (in the Git Integration issue view) that match a defined pattern using a regular expression. This is helpful for customers who want to hide intermediate pull requests when using merge queueing.

GitLab Integration Support:

• GitLab legacy integrations (e.g. API v3) are deprecated and will be removed in 2024. Please use GitLab API v4 for your integrations.
  • This is due to GitLab Legacy routes being removed in GitLab 15.9 (see GitLab article here).
  • Newly detected nested repositories of GitLab Legacy integrations will have new GitLab 9.# web linking, which is wrong for GitLab 8.# and older versions.
  • Some existing gitlab.com web links (that resulted in a 404 error) for already connected repositories are migrated to the new format in 4.19.1

v4.19.1

Feature Improvement:

• Added a pull request filter to the Integration Features Settings page. This allows Admins to hide pull requests (in the Git Integration issue view) that match a defined pattern using a regular expression. This is helpful for customers who want to hide intermediate pull requests when using merge queueing.

GitLab Integration Support:

• GitLab legacy integrations (e.g. API v3) are deprecated and will be removed in 2024. Please use GitLab API v4 for your integrations.
  • This is due to GitLab Legacy routes being removed in GitLab 15.9 (see GitLab article here).
  • Newly detected nested repositories of GitLab Legacy integrations will have new GitLab 9.# web linking, which is wrong for GitLab 8.# and older versions.
  • Some existing gitlab.com web links (that resulted in a 404 error) for already connected repositories are migrated to the new format in 4.19.1

v4.18

• Added compatibility for Jira 9.8
• Minor bug fixes and UI improvements

v4.18

• Added compatibility for Jira 9.8
• Minor bug fixes and UI improvements

v4.17

Feature Improvements:

- View main branch in panel: Added a new setting under Git integration panel – “Show main branch under branch section on Issue Web Panel”. This is useful for seeing commits for those using trunk based development.

- API Update: Added a ‘priority’ parameter to the ‘/index’ REST API. This parameter can be any positive integer and provides finer control of the indexing queue. See the help article for more information on priority values.

- Deprecating Reindex API (/rest/gitplugin/1.0/index.json). The new version is located at /rest/gitplugin/2.0/reindex. See help article for more info.

- RepoId parameter changed to Single Integer number (represents repository Id, optional. If omitted leads to reindex all repositories)

Bug Fixes / General Improvements:

- Improved CPU usage for large Jira user instances (100,000+)

- Corrected an issue where GitHub and GitLab web links were not formed correctly

- Corrected an issue where the indexing log page was not loading

v4.17

Feature Improvements:

- View main branch in panel: Added a new setting under Git integration panel – “Show main branch under branch section on Issue Web Panel”. This is useful for seeing commits for those using trunk based development.

- API Update: Added a ‘priority’ parameter to the ‘/index’ REST API. This parameter can be any positive integer and provides finer control of the indexing queue. See the help article for more information on priority values.

- Deprecating Reindex API (/rest/gitplugin/1.0/index.json). The new version is located at /rest/gitplugin/2.0/reindex. See help article for more info.

- RepoId parameter changed to Single Integer number (represents repository Id, optional. If omitted leads to reindex all repositories)

Bug Fixes / General Improvements:

- Improved CPU usage for large Jira user instances (100,000+)

- Corrected an issue where GitHub and GitLab web links were not formed correctly

- Corrected an issue where the indexing log page was not loading

v4.16

• Internal improvements

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.16

• Internal improvements

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.15

• New feature - GitLens Deep Linking: This workflow improvement is a great addition for developers that are using Visual Studio Code to edit source code. From within Jira, clicking on the GitLens icon next to repositories, commits, tags, and branches will open them in VS Code. This enables team members to quickly transition between Jira and their code editor without losing context. GitLens deep links are located within Jira issues and the Repository Browser. See help article for more info.
• Bug fix: Resolved an issue that was causing the log to flood with warning messages

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.15

• New feature - GitLens Deep Linking: This workflow improvement is a great addition for developers that are using Visual Studio Code to edit source code. From within Jira, clicking on the GitLens icon next to repositories, commits, tags, and branches will open them in VS Code. This enables team members to quickly transition between Jira and their code editor without losing context. GitLens deep links are located within Jira issues and the Repository Browser. See help article for more info.
• Bug fix: Resolved an issue that was causing the log to flood with warning messages

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.14

• Fixed an issue that resulted in an error with scheduled indexing
• Minor bug fixes

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.14

• Fixed an issue that resulted in an error with scheduled indexing
• Minor bug fixes

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.13

• When migrating to a different server, added a convenient way to update Jira home path
• Updated how last run duration is calculated in the indexing queue viewer
• Corrected an issue with Automation triggers UI for project admins

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.13

• When migrating to a different server, added a convenient way to update Jira home path
• Updated how last run duration is calculated in the indexing queue viewer
• Corrected an issue with Automation triggers UI for project admins

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.12.0.1

• Added a new page - Indexing queue - which allows you to easily view upcoming and in-progress tasks such as repository indexing and garbage collection.
  • This provides greater visibility into what's happening with your repositories and system resources.
  • Displays detailed information about the tasks - which node it was processed on, start time, finish time, processing time, task id, and more.
  • See which tasks are in the queue, find specific tasks by history, and filter tasks by specific parameters.

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.12.0.1

• Added a new page - Indexing queue - which allows you to easily view upcoming and in-progress tasks such as repository indexing and garbage collection.
  • This provides greater visibility into what's happening with your repositories and system resources.
  • Displays detailed information about the tasks - which node it was processed on, start time, finish time, processing time, task id, and more.
  • See which tasks are in the queue, find specific tasks by history, and filter tasks by specific parameters.

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.11

• Fixed a bug where the Git Integration for Jira plugin could not be enabled after installing on Jira Data Center

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.11

• Fixed a bug where the Git Integration for Jira plugin could not be enabled after installing on Jira Data Center

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.10

• Security improvements
• Bug fixes
• Updated localization strings

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.10

• Security improvements
• Bug fixes
• Updated localization strings

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.9

• Improved performance of enabling the app when a large number of repositories are configured by moving repository initialization away from plugin startup.
• Corrected placeholder text that was appearing on the connection settings page for GitLab
• Logging improvements for GitHub

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.9

• Improved performance of enabling the app when a large number of repositories are configured by moving repository initialization away from plugin startup.
• Corrected placeholder text that was appearing on the connection settings page for GitLab
• Logging improvements for GitHub

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.8.1

• Bug fix for annotated nested tags

v4.8

• Added a JMESPath Filter for the Github App integration type. You can now filter API results to limit which repositories are integrated by using a JMESPath expression (query language for JSON).

• Updated page names to follow a consistent format of GIJ*.jspa to help with scanning logs. Note:
  • Please update any Git Integration for Jira page bookmarks you may have made, as they will possibly result in a 404 error.
  • If using GitHub App integration, please update “Setup URL” to https://{yourJiraBaseUrl}/secure/GIJGitHubApps.jspa in the GitHub application general setting page (in GitHub).
• Cross-site scripting security improvements
• Jira 9.3 compatibility

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.8.1

• Bug fix for annotated nested tags

v4.8

• Added a JMESPath Filter for the Github App integration type. You can now filter API results to limit which repositories are integrated by using a JMESPath expression (query language for JSON).

• Updated page names to follow a consistent format of GIJ*.jspa to help with scanning logs. Note:
  • Please update any Git Integration for Jira page bookmarks you may have made, as they will possibly result in a 404 error.
  • If using GitHub App integration, please update “Setup URL” to https://{yourJiraBaseUrl}/secure/GIJGitHubApps.jspa in the GitHub application general setting page (in GitHub).
• Cross-site scripting security improvements
• Jira 9.3 compatibility

Note: When migrating to Jira 9 please perform the following migration steps for the plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.8

• Feature improvement: Added a JMESPath Filter for the Github App integration type. You can now filter API results to limit which repositories are integrated by using a JMESPath expression (query language for JSON).

• Updated page names to follow a consistent format of GIJ*.jspa to help with scanning logs. Note:
  • Please update any Git Integration for Jira page bookmarks you may have made, as they will possibly result in a 404 error.
  • If using GitHub App integration, please update “Setup URL” to https://{yourJiraBaseUrl}/secure/GIJGitHubApps.jspa in the GitHub application general setting page (in GitHub).
• Cross-site scripting security improvements
• Jira 9.3 compatibility

Note: When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.8

• Feature improvement: Added a JMESPath Filter for the Github App integration type. You can now filter API results to limit which repositories are integrated by using a JMESPath expression (query language for JSON).

• Updated page names to follow a consistent format of GIJ*.jspa to help with scanning logs. Note:
  • Please update any Git Integration for Jira page bookmarks you may have made, as they will possibly result in a 404 error.
  • If using GitHub App integration, please update “Setup URL” to https://{yourJiraBaseUrl}/secure/GIJGitHubApps.jspa in the GitHub application general setting page (in GitHub).
• Cross-site scripting security improvements
• Jira 9.3 compatibility

Note: When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:

• • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information

v4.7.1

• Bug fixes

v4.7

• New features
  • Git Tags processing: New tags reindexing algorithm improves performance and stability, allowing faster loading of tags on the Jira issue page
  • Reset indexes: Jira administrator can start the reset index process for all repositories using "Reset all indexes" in the "Indexing" dropdown menu
• Improvements:
  • Allow Jira admins to remove GitHub App integrations in the ‘Installing’ state using the Remove option.
  • Support for Jira 9.2
• Data Center specific:
  • Optimization for updating objects/caches on the General Settings page. Now only changed settings will trigger an update.

• When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:
  • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.7.1

• Bug fixes

v4.7

• New features
  • Git Tags processing: New tags reindexing algorithm improves performance and stability, allowing faster loading of tags on the Jira issue page
  • Reset indexes: Jira administrator can start the reset index process for all repositories using "Reset all indexes" in the "Indexing" dropdown menu
• Improvements:
  • Allow Jira admins to remove GitHub App integrations in the ‘Installing’ state using the Remove option.
  • Support for Jira 9.2
• Data Center specific:
  • Optimization for updating objects/caches on the General Settings page. Now only changed settings will trigger an update.

• When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:
  • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

v4.7

• New features
  • Git Tags processing: New tags reindexing algorithm improves performance and stability, allowing faster loading of tags on the Jira issue page
  • Reset indexes: Jira administrator can start the reset index process for all repositories using "Reset all indexes" in the "Indexing" dropdown menu
• Improvements:
  • Allow Jira admins to remove GitHub App integrations in the ‘Installing’ state using the Remove option.
  • Support for Jira 9.2
• Data Center specific:
  • Optimization for updating objects/caches on the General Settings page. Now only changed settings will trigger an update.
• When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:
  • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.7

• New features
  • Git Tags processing: New tags reindexing algorithm improves performance and stability, allowing faster loading of tags on the Jira issue page
  • Reset indexes: Jira administrator can start the reset index process for all repositories using "Reset all indexes" in the "Indexing" dropdown menu
• Improvements:
  • Allow Jira admins to remove GitHub App integrations in the ‘Installing’ state using the Remove option.
  • Support for Jira 9.2
• Data Center specific:
  • Optimization for updating objects/caches on the General Settings page. Now only changed settings will trigger an update.
• When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:
  • Run the 'Reset all indexes’ for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v 4.6

• New integration - GitHub App - provides additional authentication and control options. This eliminates the reliance on a specific GitHub user's permissions/access for the integration. Benefits over OAuth include:
  • A GitHub App uses its own identity vs. an OAuth app (which acts as a GitHub user)
  • Determine repository access at the organization or repository level for the integration
  • Uses granular permissions that allow the app to request access only to what it needs (e.g. read access to metadata)
  • Offers a higher rate limit vs. OAuth
  • For more details, see the Help Article | GitHub Article
• When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:
  • Run the 'Reset index' for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v 4.6

• New integration - GitHub App - provides additional authentication and control options. This eliminates the reliance on a specific GitHub user's permissions/access for the integration. Benefits over OAuth include:
  • A GitHub App uses its own identity vs. an OAuth app (which acts as a GitHub user)
  • Determine repository access at the organization or repository level for the integration
  • Uses granular permissions that allow the app to request access only to what it needs (e.g. read access to metadata)
  • Offers a higher rate limit vs. OAuth
  • For more details, see the Help Article | GitHub Article
• When migrating to Jira 9 please perform the following migration steps for the Git Integration for Jira plugin:
  • Run the 'Reset index' for all repositories/integrations.
  • Check the "Reverse commit tab sort order" option in the plugin "General settings".
  • See the corresponding migration article for more information.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.5.2.1

Fixed performance issue for issues with no commits associated.

v4.5.1.1

Fixed compatibility issue where Git Integration for Jira interfered with 3rd party applications integrating with Automation for Jira in Jira 9.x.

v4.5.1

New feature: ScriptRunner integration

Automate and extend Jira even further using Adaptavist’s ScriptRunner using easy to consume Git Integration for Jira (GIJ) APIs. We’ve made it very easy to script using GIJ’s APIs.

For more information about how to use ScriptRunner with commits, branches, tags and more - see our documentation at the GitKraken Help Center.

Need help setting up ScriptRunner to use Git data? Be sure to schedule a one-on-one review session with one of our experts

Other changes:

• 8 bug fixes including a fix for conflict with the Power Scripts plugin

• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.5.2.1

Fixed performance issue for issues with no commits associated.

v4.5.1.1

Fixed compatibility issue where Git Integration for Jira interfered with 3rd party applications integrating with Automation for Jira in Jira 9.x.

v4.5.1

New feature: ScriptRunner integration

Automate and extend Jira even further using Adaptavist’s ScriptRunner using easy to consume Git Integration for Jira (GIJ) APIs. We’ve made it very easy to script using GIJ’s APIs.

For more information about how to use ScriptRunner with commits, branches, tags and more - see our documentation at the GitKraken Help Center.

Need help setting up ScriptRunner to use Git data? Be sure to schedule a one-on-one review session with one of our experts

Other changes:

• 8 bug fixes including a fix for conflict with the Power Scripts plugin

• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.5.1.1

Fixed compatibility issue where Git Integration for Jira interfered with 3rd party applications integrating with Automation for Jira in Jira 9.x.

v4.5.1

New feature: ScriptRunner integration

Automate and extend Jira even further using Adaptavist’s ScriptRunner using easy to consume Git Integration for Jira (GIJ) APIs. We’ve made it very easy to script using GIJ’s APIs.

For more information about how to use ScriptRunner with commits, branches, tags and more - see our documentation at the GitKraken Help Center.

Need help setting up ScriptRunner to use Git data? Be sure to schedule a one-on-one review session with one of our experts

Other changes:

• 8 bug fixes including a fix for conflict with the Power Scripts plugin

• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.5.1.1

Fixed compatibility issue where Git Integration for Jira interfered with 3rd party applications integrating with Automation for Jira in Jira 9.x.

v4.5.1

New feature: ScriptRunner integration

Automate and extend Jira even further using Adaptavist’s ScriptRunner using easy to consume Git Integration for Jira (GIJ) APIs. We’ve made it very easy to script using GIJ’s APIs.

For more information about how to use ScriptRunner with commits, branches, tags and more - see our documentation at the GitKraken Help Center.

Need help setting up ScriptRunner to use Git data? Be sure to schedule a one-on-one review session with one of our experts

Other changes:

• 8 bug fixes including a fix for conflict with the Power Scripts plugin

• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.5.1

New feature: ScriptRunner integration

Automate and extend Jira even further using Adaptavist’s ScriptRunner using easy to consume Git Integration for Jira (GIJ) APIs. We’ve made it very easy to script using GIJ’s APIs.

For more information about how to use ScriptRunner with commits, branches, tags and more - see our documentation at the GitKraken Help Center.

Need help setting up ScriptRunner to use Git data? Be sure to schedule a one-on-one review session with one of our experts

Other changes:

• 8 bug fixes including a fix for conflict with the Power Scripts plugin

• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

New feature: ScriptRunner integration

Automate and extend Jira even further using Adaptavist’s ScriptRunner using easy to consume Git Integration for Jira (GIJ) APIs. We’ve made it very easy to script using GIJ’s APIs.

For more information about how to use ScriptRunner with commits, branches, tags and more - see our documentation at the GitKraken Help Center.

Need help setting up ScriptRunner to use Git data? Be sure to schedule a one-on-one review session with one of our experts

Other changes:

• 8 bug fixes including a fix for conflict with the Power Scripts plugin

• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.4

Jira 9.0 compatibility

Important feature note: Jira 9.0 includes native Automation for Jira (A4J) support in Jira Data Center. Git Integration for Jira Includes six (6) new DevOps triggers for use with A4J.

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.4

Jira 9.0 compatibility

Important feature note: Jira 9.0 includes native Automation for Jira (A4J) support in Jira Data Center. Git Integration for Jira Includes six (6) new DevOps triggers for use with A4J.

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.3 - Maintenance release

• Improve Git tags calculation (more improvements in coming weeks)
• Other bug fixes

v4.3.2

New Feature:

• GitLab/Azure Repos permission enforcement for users

Improvements:

• Widened Create Branch / Pull Request dialogs and added hover support for long repository and branch names.
• Azure Repos and Gerrit groups urls show more consistently.
• Minified some files.

v4.3.1

New Feature: Repository Names

• For GitHub, GitLab, Azure DevOps, Microsoft VSTS and TFS, GIJ will now show the git service icon + the organization, group, or account/collection will be shown when the name of the repository is shown.

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.3 - Maintenance release

• Improve Git tags calculation (more improvements in coming weeks)
• Other bug fixes

v4.3.2

New Feature:

• GitLab/Azure Repos permission enforcement for users

Improvements:

• Widened Create Branch / Pull Request dialogs and added hover support for long repository and branch names.
• Azure Repos and Gerrit groups urls show more consistently.
• Minified some files.

v4.3.1

New Feature: Repository Names

• For GitHub, GitLab, Azure DevOps, Microsoft VSTS and TFS, GIJ will now show the git service icon + the organization, group, or account/collection will be shown when the name of the repository is shown.

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.2

New Feature:

• GitLab/Azure Repos permission enforcement for users

Improvements:

• Widened Create Branch / Pull Request dialogs and added hover support for long repository and branch names.
• Azure Repos and Gerrit groups urls show more consistently.
• Minified some files.

v4.3.1

New Feature: Repository Names

• For GitHub, GitLab, Azure DevOps, Microsoft VSTS and TFS, GIJ will now show the git service icon + the organization, group, or account/collection will be shown when the name of the repository is shown.

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.2

New Feature:

• GitLab/Azure Repos permission enforcement for users

Improvements:

• Widened Create Branch / Pull Request dialogs and added hover support for long repository and branch names.
• Azure Repos and Gerrit groups urls show more consistently.
• Minified some files.

v4.3.1

New Feature: Repository Names

• For GitHub, GitLab, Azure DevOps, Microsoft VSTS and TFS, GIJ will now show the git service icon + the organization, group, or account/collection will be shown when the name of the repository is shown.

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.1

New Feature: Repository Names

• For GitHub, GitLab, Azure DevOps, Microsoft VSTS and TFS, GIJ will now show the git service icon + the organization, group, or account/collection will be shown when the name of the repository is shown.

Improvements

• Improved handling of webhook threads
• Improved handling of AWS CodeCommit webhooks

v4.3.0.1

• Improved detection of the Automation for Jira app (and absence of app).

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Fixed:
  • Tracked folder creation with empty path
  • ‘Require User PAT’ incorrectly saved when changing integration settings
  • Empty Jira issue key when creating a new branch from a board view
  • Improved logging when repository/integration is removed

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.1

New Feature: Repository Names

• For GitHub, GitLab, Azure DevOps, Microsoft VSTS and TFS, GIJ will now show the git service icon + the organization, group, or account/collection will be shown when the name of the repository is shown.

Improvements

• Improved handling of webhook threads
• Improved handling of AWS CodeCommit webhooks

v4.3.0.1

• Improved detection of the Automation for Jira app (and absence of app).

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Fixed:
  • Tracked folder creation with empty path
  • ‘Require User PAT’ incorrectly saved when changing integration settings
  • Empty Jira issue key when creating a new branch from a board view
  • Improved logging when repository/integration is removed

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.0.1

• Improved detection of the Automation for Jira app (and absence of app).

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Fixed:
  • Tracked folder creation with empty path
  • ‘Require User PAT’ incorrectly saved when changing integration settings
  • Empty Jira issue key when creating a new branch from a board view
  • Improved logging when repository/integration is removed

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.3.0.1

• Improved detection of the Automation for Jira app (and absence of app).

v4.3

New Feature: Support for Automation for Jira (separate app)

• Automate your Jira workflows with new triggers offered in new "DevOps" category (screenshot):
  • Branch Created
  • Commit Created
  • Pull Request Created
  • Pull Request Declined
  • Pull Request Merged
• Fixed:
  • Tracked folder creation with empty path
  • ‘Require User PAT’ incorrectly saved when changing integration settings
  • Empty Jira issue key when creating a new branch from a board view
  • Improved logging when repository/integration is removed

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.2.1

• Bug fixes

v4.2.0.4

• Fixed: Enabling "Require personal access tokens" along with project permissions blocked the Create branch feature.

v4.2

New Feature

• Dedicated indexing nodes for Jira Data Center
  • Specify specific DC nodes to perform Git Integration for Jira indexing jobs. Screenshot
  • New setting available in General settings (default is all available Data Center nodes).

Improvements:

• Suggest Jira users enter a Jira issue key if no issue key detected when creating a branch or pull request.
• Updated GitHub integration names to reflect new naming conventions between Cloud and self-hosted.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.2.1

• Bug fixes

v4.2.0.4

• Fixed: Enabling "Require personal access tokens" along with project permissions blocked the Create branch feature.

v4.2

New Feature

• Dedicated indexing nodes for Jira Data Center
  • Specify specific DC nodes to perform Git Integration for Jira indexing jobs. Screenshot
  • New setting available in General settings (default is all available Data Center nodes).

Improvements:

• Suggest Jira users enter a Jira issue key if no issue key detected when creating a branch or pull request.
• Updated GitHub integration names to reflect new naming conventions between Cloud and self-hosted.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.2.0.4

• Fixed: Enabling "Require personal access tokens" along with project permissions blocked the Create branch feature.

v4.2

New Feature

• Dedicated indexing nodes for Jira Data Center
  • Specify specific DC nodes to perform Git Integration for Jira indexing jobs. Screenshot
  • New setting available in General settings (default is all available Data Center nodes).

Improvements:

• Suggest Jira users enter a Jira issue key if no issue key detected when creating a branch or pull request.
• Updated GitHub integration names to reflect new naming conventions between Cloud and self-hosted.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.2.0.4

• Fixed: Enabling "Require personal access tokens" along with project permissions blocked the Create branch feature.

v4.2

New Feature

• Dedicated indexing nodes for Jira Data Center
  • Specify specific DC nodes to perform Git Integration for Jira indexing jobs. Screenshot
  • New setting available in General settings (default is all available Data Center nodes).

Improvements:

• Suggest Jira users enter a Jira issue key if no issue key detected when creating a branch or pull request.
• Updated GitHub integration names to reflect new naming conventions between Cloud and self-hosted.

Need help? Schedule a one-on-one system review

Report issues to support@bigbrassband.com

v4.1.5

• New feature: Added support for the SSH Config File when connecting repositories via SSH.
• Fixed: Stored XSS via Display Name

v4.1.4

• Jira administrators can require Jira users to provide a GitHub personal access token to verify repository permission to view all development information provided by the Git Integration for Jira app.
• When enabled, GitHub permissions are required to see: Repositories, Commits, Branches, Pull Requests and Tags.
• Unique to our Jira Data Center and Jira Server product.
• Limited to GitHub.com and GitHub Enterprise Server. Support for GitLab and Azure DevOps available at a later date. See roadmap for more information.
• Permissions are cached and maintained. Cache interval (in hours) is a setting available to the Jira administrator.
• To learn more about Enforcing GitHub permissions, see our documentation.

Need help? Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.1.5

• New feature: Added support for the SSH Config File when connecting repositories via SSH.
• Fixed: Stored XSS via Display Name

v4.1.4

• Jira administrators can require Jira users to provide a GitHub personal access token to verify repository permission to view all development information provided by the Git Integration for Jira app.
• When enabled, GitHub permissions are required to see: Repositories, Commits, Branches, Pull Requests and Tags.
• Unique to our Jira Data Center and Jira Server product.
• Limited to GitHub.com and GitHub Enterprise Server. Support for GitLab and Azure DevOps available at a later date. See roadmap for more information.
• Permissions are cached and maintained. Cache interval (in hours) is a setting available to the Jira administrator.
• To learn more about Enforcing GitHub permissions, see our documentation.

Need help? Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.1.4

• Jira administrators can require Jira users to provide a GitHub personal access token to verify repository permission to view all development information provided by the Git Integration for Jira app.
• When enabled, GitHub permissions are required to see: Repositories, Commits, Branches, Pull Requests and Tags.
• Unique to our Jira Data Center and Jira Server product.
• Limited to GitHub.com and GitHub Enterprise Server. Support for GitLab and Azure DevOps available at a later date. See roadmap for more information.
• Permissions are cached and maintained. Cache interval (in hours) is a setting available to the Jira administrator.
• To learn more about Enforcing GitHub permissions, see our documentation.

Need help? Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.1.4

• Jira administrators can require Jira users to provide a GitHub personal access token to verify repository permission to view all development information provided by the Git Integration for Jira app.
• When enabled, GitHub permissions are required to see: Repositories, Commits, Branches, Pull Requests and Tags.
• Unique to our Jira Data Center and Jira Server product.
• Limited to GitHub.com and GitHub Enterprise Server. Support for GitLab and Azure DevOps available at a later date. See roadmap for more information.
• Permissions are cached and maintained. Cache interval (in hours) is a setting available to the Jira administrator.
• To learn more about Enforcing GitHub permissions, see our documentation.

Need help? Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.5

• Performance fix when loading Git Commits issue tab when many repositories configured. Reverting pagination.

v4.0.1-4.0.4

• The 'Discard clone files' that was introduced in version 2.12 and remained a Beta feature is deprecated and will be removed after August 15, 2022.

• Bug fixes

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.5

• Performance fix when loading Git Commits issue tab when many repositories configured. Reverting pagination.

v4.0.1-4.0.4

• The 'Discard clone files' that was introduced in version 2.12 and remained a Beta feature is deprecated and will be removed after August 15, 2022.

• Bug fixes

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.4

• The 'Discard clone files' that was introduced in version 2.12 and remained a Beta feature is deprecated and will be removed after August 15, 2022.
• Bug fix for issues disappearing from board after associating commit with Jira issue

v4.0.1-4.0.3

• Bug fixes

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.4

• The 'Discard clone files' that was introduced in version 2.12 and remained a Beta feature is deprecated and will be removed after August 15, 2022.
• Bug fix for issues disappearing from board after associating commit with Jira issue

v4.0.1-4.0.3

• Bug fixes

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.3

• 2 bug fixes

v4.0.2

• 7 bug fixes

v4.0.1

• 9 bug fixes
• Moved some General settings into an advanced menu

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.3

• 2 bug fixes

v4.0.2

• 7 bug fixes

v4.0.1

• 9 bug fixes
• Moved some General settings into an advanced menu

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.2

• 7 bug fixes

v4.0.1

• 9 bug fixes
• Moved some General settings into an advanced menu

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.2

• 7 bug fixes

v4.0.1

• 9 bug fixes
• Moved some General settings into an advanced menu

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.1

• 9 bug fixes
• Moved some General settings into an advanced menu

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v4.0.1

• 9 bug fixes
• Moved some General settings into an advanced menu

v4.0

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

See release blog post for Improvements.

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

Improvements

• Renamed “Repository browser”
• Pull requests are sorted by status (Jira issue)
• Improvement in tag calculation performance
• All credentials are encrypted in Jira database

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

New indexing features

• Indexing queue moved to Jira database.
• Skipping: repeated repositories are not added to the queue.
• Sleep: New setting for Webhooks to prevent repositories from being added too often.
• Prioritized queue: Manual and REST then webhooks and then scheduled.
• Initial integration scanning is moved into a separate thread and performed independently of other reindexing operations.

Data Center

• Queue shared between all Data Center nodes.
• Each node has a separate indexing job thread for faster indexing times.

New Features

• New indexing statuses
• Git Commits issue tab is now paginated (Jira issue)
• ${basebranch} available in Branch name template (General settings)

Improvements

• Renamed “Repository browser”
• Pull requests are sorted by status (Jira issue)
• Improvement in tag calculation performance
• All credentials are encrypted in Jira database

Notes

• Jira 8 required
• Review on test/non-production Jira instance first.

Schedule a one-on-one review

Report issues to support@bigbrassband.com

v3.9.1.2

• Fixed commit email sending (broken in v3.9.0.2)

v3.9.1.1

• Improved database support for GIJ General settings

v3.9.1

• Large numbers of repositories (over 1000) will load much faster in the Repository Browser.

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.9.1.2

• Fixed commit email sending (broken in v3.9.0.2)

v3.9.1.1

• Improved database support for GIJ General settings

v3.9.1

• Large numbers of repositories (over 1000) will load much faster in the Repository Browser.

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.9.1.1

• Improved database support for GIJ General settings

v3.9.1

• Large numbers of repositories (over 1000) will load much faster in the Repository Browser.

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.9.1.1

• Improved database support for GIJ General settings

v3.9.1

• Large numbers of repositories (over 1000) will load much faster in the Repository Browser.

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.9.1

Large numbers of repositories (over 1000) will load much faster in the Repository Browser.

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.9.1

Large numbers of repositories (over 1000) will load much faster in the Repository Browser.

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.9.0.2

New Feature: Deep linking to GitKraken Git client

• Open commits, branches, tags and repositories directly in GitKraken from the Jira issue view giving you a seamless transition from your Jira issues to GitKraken.
• Deep linking can be disabled by Jira administrators.
• Learn more about this feature

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.9.0.2

New Feature: Deep linking to GitKraken Git client

• Open commits, branches, tags and repositories directly in GitKraken from the Jira issue view giving you a seamless transition from your Jira issues to GitKraken.
• Deep linking can be disabled by Jira administrators.
• Learn more about this feature

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.8.1

New Features

3 new General settings features to give Jira administrators more control over settings previously managed at the integration/repository level.

• General setting: Enable/disable Repository Browser across Git Integration for Jira. Disabling this feature will remove the "Git" Jira header menu for all Jira users except Jira administrators.
• General setting: Enable/disable Source code diff viewing across

  Git Integration for Jira.

• General setting: Require Jira users to provide a Personal Access Token (PAT) across Git Integration for Jira when creating branches/pull requests in Jira.

Report issues to support@bigbrassband.com

Future releases: Roadmap

v3.8.1

New Features

3 new General settings features to give Jira administrators more control over settings previously managed at the integration/repository level.

• General setting: Enable/disable Repository Browser across Git Integration for Jira. Disabling this feature will remove the "Git" Jira header menu for all Jira users except Jira administrators.
• General setting: Enable/disable Source code diff viewing across

  Git Integration for Jira.

• General setting: Require Jira users to provide a Personal Access Token (PAT)across Git Integration for Jira when creating branches/pull requests in Jira.

Report issues to support@bigbrassband.com

Future releases: Roadmap