From the built-in browser

From time to time, the developers can make mistakes relating commits to issues because of missing, wrong or misspelling issue keys in Subversion commits.

This requires to fix the comment from the Subversion repository and also in Subversion ALM. 

In previous versions, this required upgrading the related issues directly from the Jira database or re-index all the repository by removing and registering the repository again.

Since the 8.4 version, it is possible to refresh the related issues from Subversion ALM directly in a straightforward way by navigating to the fixed revision:

and then clicking on the Refresh Issues button:

This will re-scan the commit message and replace the existing related issues by the new ones.

From a form URL

If a repository is accessed via svn+ssh protocol or if the organization has configured the repository to use a third-party web client for Subversion  via web links then it is not possible to refresh the issues related to a revision.

A new form is available for this purpose accessible from this URL:

${JIRA_BASE_URL}/secure/SVNALMUpdateCommits!default.jspa

It allows granted users to re-scan a concrete revision on a Subversion repository and refresh the issues related to it without having to reindex the full repository.

Jira administrators can control the users that can do it. A new configuration parameter is supported for this. Only the users belonging to this group can reindex commit messages.

Tip: If the development project is related to a one Subversion repository, a link can be created in the project to open the Refresh Issues page with the repository selected by default by appending it as a parameter to the URL:

${JIRA_BASE_URL}/secure/SVNALMUpdateCommits!default.jspa?repository=<RepositoryId>