how to cross jira and svn effectively

The initial problem is that we want to link the commit in SVN with JIRA tickets, and:
1. Should not skip the commits without really existing tickets in Jira
2. Directly in Jira there should be an opportunity to see what (who, when ...) is commited in SVN to the context of a particular ticket.

As it turned out, it's not so easy to google info on this topic. There are a lot of jira pre-commit hooks solutions, but only one (maybe there are others?!, But I did not find it) allows you to solve the problem of “real-life tickets in Jira”. And so decisions ...


According to the first task.
JIRA Commit Acceptance Plugin
Installation is described there. The only thing not:
- do chmod + x on scripts
- ln -s pre-commit.sh pre-commit
- Python script why not smell, barley like a glove
- Do not forget to add your paths + settings to the scripts (in both)
- Read the docks to the end!
')
How is it better to just hooks svn. This hook asks Jira (via RPC), and does not draw conclusions on the regular schedule. Accordingly, all settings are done through the Jira admin:
- for which projects include hooks
- Prohibit commits to closed tickets
- Whether to ban comits, if the author of the comit and performer of the ticket are different.

According to the second.
JIRA Subversion Plugin
Everything is simple, only:
- Pay attention to the table of correspondence of versions of a plug-in and Jira
- Install WebSVN or equivalent (optional if you do not need to view the file in the browser)
- To rebuild indexes from SVN, you must delete the folder / plugins / atlassian-subversion-revisions / (attention, not only files)