3rd Party Version Control Integration in JIRA

What are the important items that are required to be considered when integrating a new version control software into JIRA? Is it to be done only via FishEye?

3 answers

1 accepted

1 vote
Answer accepted


What are you looking for?

A) Improve the SUBVERSION from a reporting point of view -> FishEye (commercial)

B) Improve traceability betwen JIRA and Subversion -> JIRA Subversion plug-in (free) or this alternative and also free fork of the plug-in (the link might be broken until it is approved. In the meanwhile, you can build the plugin from the sources at https://bitbucket.org/pbeltranl/jira-subversion-plugin-plus)


1) Of course, with FishEye you also get B).

2) Why might you want to use the fork?

  • It is a fork of the Atlassian's plug-in and it supports the v2 plug-ins system (no JIRA re-start required). This is a feature that the Atlassian plug-in will support in the 0.10.12 version, but not relased yet.
  • It is open source and free.
  • It's fully compatible with any current repositoy configuration.
  • It indexes the FULL history of the repository rather than those commits related to JIRA only.
  • It replaces the Lucene index by an Apache Derby database, so you can get a lot of information with standard SQL and build your own reporting system around Subversion.
  • It gets the Subversion metadata from the cache rather than calling Subversion everytime (it can improve a lot the performance an the plug-in and also show useful results even with Subvesion shutdown)

Exmaple of use: if you want to get the commits by author and repository it would be as simple as query for:

select count(*), author, repoId from CACHE.REVISIONS group by author, repoId

and get the results from the user interface in order to show them on any fancy stuff like a pie chart or table.

Hope this helps,


For Subversion only ;)

0 votes

You don't have to use Fisheye, there are other options (e.g. the subversion plugin shows displays commit information on issues and projects). But the only useful answer we can give to this question really is "The important item is how your users want to use it"

Good insights into subversion integration. How do I integrate other version control products (for which there are no direct interface or plugin) ?

One technique seems to be via emails. Create issues via emails and update comments based on the subject field.

Is there any other method that can be utilized to develop the interface?


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


242 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you