Notable improvements are:

• Important: Dropped support for Jira 7. We support only the two last major versions - 8 and 9. Support of Jira 7 makes the development and support very complex and error-prone.
• Improvement: Indexation improvements. New commits are put in front of the old commits to speed up the more relevant commit and pull request indexing.

Notable improvements are:

• Important: Dropped support for Jira 7. We support only the two last major versions - 8 and 9. Support of Jira 7 makes the development and support very complex and error-prone.
• Improvement: Indexation improvements. New commits are put in front of the old commits to speed up the more relevant commit and pull request indexing.

Notable improvements are:

• IMPROVEMENT: Gerrit integration performance improvements - Etags usage and cache optimization.

Jira Gitlab Github Gerrit integration release notes.

Gerrit Jira integration guide.

Notable improvements are:

• IMPROVEMENT: Gerrit integration performance improvements - Etags usage and cache optimization.

Jira Gitlab Github Gerrit integration release notes.

Gerrit Jira integration guide.

Notable improvements are:

• IMPROVEMENT: Gerrit integration performance improvements - Etags usage and cache optimization.

Jira Gitlab Github Gerrit integration release notes.

Gerrit Jira integration guide.

Notable improvements are:

• IMPROVEMENT: Gerrit integration performance improvements - Etags usage and cache optimization.

Jira Gitlab Github Gerrit integration release notes.

Gerrit Jira integration guide.

Notable improvements are:

• Improvement: Added links to the help centre and support.
• Improvement: Gerrit performance improvements.
• Improvement: Gerrit cache duration setting added.
• Improvement: Gerrit issue key search setting added - now you can configure where in Gerrit the issue key should be searched.

Notable improvements are:

• Improvement: Added links to the help centre and support.
• Improvement: Gerrit performance improvements.
• Improvement: Gerrit cache duration setting added.
• Improvement: Gerrit issue key search setting added - now you can configure where in Gerrit the issue key should be searched.

https://help.moveworkforward.com/JIGIT/jigit-jira-gerrit-code-review-support

Notable improvements are:

• Improvement: The test connection button behaves more predictable.
• Improvement: Repository names for commit and pull request messages contain proper repository name.
• Security: Updated 3rd party dependencies to have the latest patched version.

Notable improvements are:

• Improvement: The test connection button behaves more predictable.
• Improvement: Repository names for commit and pull request messages contain proper repository name.
• Security: Updated 3rd party dependencies to have the latest patched version.

Notable improvements are:

• Improvement: Jigit Development Panel displays the issue related branches and pull requests (by the issue key).
• Bug fix: Jigit Development Panel UI improvements.

Notable improvements are:

• Improvement: Jigit Development Panel displays the issue related branches and pull requests (by the issue key).
• Bug fix: Jigit Development Panel UI improvements.

Notable improvements are:

• Improvement: Gerrit REST endpoint added. More details here.
• Improvement: Gerrit summary panel added.
• Improvement: Jigit tab project allowed and disallowed list added.
• Improvement: Gerrit integration has not allowed and disallowed project lists to display or hide Gerrit integration, in particular, Jira projects.

Notable improvements are:

• Improvement: Gerrit REST endpoint added. More details here.
• Improvement: Gerrit summary panel added.
• Improvement: Jigit tab project allowed and disallowed list added.
• Improvement: Gerrit integration has not allowed and disallowed project lists to display or hide Gerrit integration, in particular, Jira projects.

Notable improvements are:

• Improvement: Added global settings to control the visibility of the Jigit Development Panel on the issue View.
• Bugfix: Rule search is case insensitive.

Notable improvements are:

• Improvement: Added global settings to control the visibility of the Jigit Development Panel on the issue View.
• Bugfix: Rule search is case insensitive.

Notable improvements are:

• Improvement: Search of the rules added.
• Improvement: Pagination of the rules added. 10 rules per page are the default.
• Improvement: Repository mask added for the group configuration type in order to reduce the scan time.
• Bugfix: From branch selection in the Dev Panel in some cases didn’t work.

Notable improvements are:

• Improvement: Search of the rules added.
• Improvement: Pagination of the rules added. 10 rules per page are the default.
• Improvement: Repository mask added for the group configuration type in order to reduce the scan time.
• Bugfix: From branch selection in the Dev Panel in some cases didn’t work.

• Dev Panel issue for issue with a short summary

• Dev Panel issue for issue with a short summary

Notable improvements are:

• Bug fix: Jigit Development panel visibility control.

Notable improvements are:

• Bugfix: Jigit Development panel visibility control.

Notable improvements are:

• New feature: Jigit Development panel on the Issue View screen that allows to see the issue related git branches and create a new feature branch.

Notable improvements are:

• New feature: Jigit Development panel on the Issue View screen that allows to see the issue related git branches and create a new feature branch.

Notable improvements are:

• Gerrit Code Review support added.
• Minor performance bug fixes.

Notable improvements are:

• Gerrit Code Review support added.
• Minor performance bug fixes.

Notable improvements are:

• Bug fixes: multiple stability improvements

Notable improvements are:

• Bug fixes: multiple stability improvements

Notable improvements are:

• Improvement: Added support for indexing of pull and merge requests. Now you can opt in to display related to the issue pull requests. Pull or merge request title should contain the issue key. For instance, DEV-123 added support for pull requests indexing for GitLab and GitHub.
• Improvement: if a repo does not contain the default branch, the setting from the configuration is used.

The app guide is here.

Notable improvements are:

• Improvement: Added support for indexing of pull and merge requests. Now you can opt in to display related to the issue pull requests. Pull or merge request title should contain the issue key. For instance, DEV-123 added support for pull requests indexing for GitLab and GitHub.
• Improvement: if a repo does not contain the default branch, the setting from the configuration is used.

The app guide is here.

• Fixed navigation for Jira 7.10

• Fixed navigation for Jira 7.10

Notable improvements are:

• Added a JQL function issuesWithCommitCount(number).
• Now the amount of not indexed yet repositories is displayed.

The release notes are here and the guide is here.

Notable improvements are:

• Added a JQL function issuesWithCommitCount(number).
• Now the amount of not indexed yet repositories is displayed.

The release notes are here and the guide is here.

• Now you can rename the configuration rules.

• Now you can rename the configuration rules.

• Improved message format for Jira comments

• Improved message format for Jira comments

• Change of the URL format to better pass parameters

Major version because the UI URLs changed, otherwise no major changes.

• Change of the URL format to better pass parameters

Major version because the UI URLs changed, otherwise no major changes.

• Added a whitelist of the projects where Jigit is allowed. The blacklist was added before.
• Added a setting that allows adding Jigit comments as a Jira comment.

• Added a whitelist of the projects where Jigit is allowed. The blacklist was added before.
• Added a setting that allows adding Jigit comments as a Jira comment.

Add a feature that allows limiting the Jira projects that can see Jigit issue view tab. Available in global settings.

Add a feature that allows limiting the Jira projects that can see Jigit issue view tab. Available in global settings.

• Added support for smart commits
• Improved REST APIs to work with the configuration

• Added support for smart commits
• Improved REST APIs to work with the configuration

• REST API to read configurations added (only for global admin) - please read more about this here.

• REST API to read configurations added (only for global admin) - please read more about this here.

Minor improvements including:

• You can configure how often reindexing is run using a env variable moveworkforward.jigit.index.interval
• Repo/rule name can now have # in the name
• Adde support indexing of branches using wildcard, e.g. hotfix/*

Minor improvements including:

• You can configure how often reindexing is run using a env variable moveworkforward.jigit.index.interval
• Repo/rule name can now have # in the name
• Adde support indexing of branches using wildcard, e.g. hotfix/*

• From this release the App is not paid anymore.
• We will provide support for free versions until the 1st of Jan 2021, however, we won't be release new functionality or bug fixes to free versions.

• Bug fix (Oracle Db only): problem getting data in some cases
• Bug fix: related to the previous (didn't default to English if there was not translation)

• Bug fix (Oracle Db only): problem getting data in some cases
• Bug fix: related to the previous (didn't default to English if there was not translation)

Hi,

In order to provide you the quality, the data center support and the support services you expect we have to change the payment model.

We will keep older versions supported and free for some time to allow gradual transition.

If you are not happy with the price and functionality please do not hesitate to reach out.

Let's Move Work Forward together.

Hi,

In order to provide you the quality, the data center support and the support services you expect we have to change the payment model.

We will keep older versions supported and free for some time to allow gradual transition.

If you are not happy with the price and functionality please do not hesitate to reach out.

Let's Move Work Forward together.

Please update if you saw an error "Application does not have a valid license. The functionality will be limited."

Please update if you couldn't connect and saw this error

org.apache.commons.io.IOUtils.close(Ljava/net/URLConnection;)V","status-code":500,"stack-trace":"java.lang.NoSuchMethodError"

The Data Center is coming. We have started the process at the beginning of May. When it is released the Data Center installations will have to use the DC compatible App.

First release by Move Work Forward.

Contact us at support@moveworkforward.com or our Service Desk if you need any new functionality or Data Center support.

In the next few months we will change the license from Apache 2.0 to the commercial license (old versions will be still available).

Bug fixes:

• Issue 91: Commit information not populating in JIRA
• Issue 92: Jigit Stopped Reindexing After Upgrading it to Version 1.2.15

Bug fixes:

• Issue 85: Add git commit identifier to errors
• Issue 90: Deleting an indexed repository gives display errors on the Jigit tab

Fixes:

• Issue 81: Issue with display order of Jigit tab panel in issue's activity log

Enhancements:

• Issue 82: Make summary output in issue tab panel more intuitive

Repository name is now a link to a repository and branch name is highlighted in bold type.

• Issue 83: Add German translation to Jigit plugin

Interface of the add-on is translated into German and Russian languages.

Issue 76: Make it interleave other comments

Version introduces redesigned issue tab with all JIRA features like sorting and integration with issue actions tab.

Bug fixes:

• Issue 73: Invalid repos or invalid default branches cause Jigit to stop indexing prematurely

Thanks Robert Wilterdink for collaboration.

New feature:

Issue 68: Support for Jira 8.0

• Issue 62: Support GitLab 8 and earlier versions

Jigit supports GitLab 8 and earlier versions. Select correspondent server type on the settings page.

Bug fixes:

• Issue 60: Jigit is not indexing more than 20 Gitlab-Branches

Bug fixes:

Issue 52 Empty diff with no files causes ExecutionException

New feature:

Jigit does not support GitLab API v3 anymore since it has been officially removed from the newest version.

Issue 46 Gitlab api v3 deprecated

New feature:

Jigit now supports GitHub Enterprise!

Issue 42 Integrate Jigit with GitHub Enterprise

Bug fixes:

Issue 43 index all repositories in a group, not only the first 20

Issue 31: BranchId must be URL encoded

Issue 29 Missing web link to commit on Jigit tab

Issue 24: Uncaught exception thrown by REST service: null

Jigit checks a default branch value of repositories inside a group and skips such repositories during indexing of commits.

Issue 25: Add INFO logging on add\delete\edit actions

Jigit logs every action with a repo at the config page with INFO level. Don't forget to enable this level for package jigit at Logging and Profiling settings page.

New feature:

Issue 12 Check Repository Group instead of specific Repository

At Release Notes page you can find detailed information about the feature and a guide on how to start using it.

Bug fixes:

• Issue 18 Error when clicking on JIGIT tab (on JIRA instances running on MS SQLServer)

Bug fixes:

• Issue 16 Error "null commit diff for sha1" while getting GitLab commit diff
• Issue 17 Wrong branch name in the list of branches interrupts indexing following branches

Jigit allows now to index all repository branches without specifying them in a separate way. Tick "Index all branches" option in "Edit" menu to enable this feature for existing repositories.

• Configuration page now displays repositories and branches (except the default branch) in lexicographical order. The default branch is always on the top.
• Bug fixes.