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