it has come back again:
don't miss the new commit graphs showing JIRA issues and with lots of filters to deal with large graphs.
I've added a lot of JQL functions to search issues based on any Subversion attribute (commit number, date, author, comment, file, directory, subdirectory and more)
The web client has also been enhance BI-directional traceability and the JIRA issues displayed while you browse on Subversion: you can now go from JIRA to Subversion and from Subversion to JIRA at any moment (and at the right place, of course)
Hopefully, a new version supporting merge will be realeased soon.
Some Notes: the add-on has been moved from vendor. However, it is free too. The backward compatibility was broken, it means you have to register your repositories again and wait for the repositories be indexed. All the source code have been reorganized and all the keys in the plugin renamed to avoid conflicts with 3rd party add-ons, so you can install the latest version without un-install the Atlassian JIRA Subversion plugin nor older versions of the Subversion Plus itself (4.x).
Hope this helps.
This mean that if I am currently using 4.0.1 version when I will install Subversion ALM from the UPM I will have two duplicated plugins, tabs, menus.. et cetera?
If so then what are the next steps? Reindexing the current repositories back again and then removing old version of the plugin?
Is there any documentation that could help understand this transition?
The short and easy way: un-install any older version and install the latest version from the Markeplace. You have to register your repositories and wait them for be indexed again which usually takes few minutes.
During this time (the transition) your users will be able to browse on Subversion because the bundled Polarion web client access to the Subversion server directly. They could not (or they could get incomplete results) working with (a) commit graphs, (b) commit calendars, (c) jql functions and (d) commits on the JIRA issue and project tabs as all those features fetch the data from the cache rather than from the Subversion server.
There are even some alternative ways to make the transition almost with 100% of availability for end users, thus they could work with the plugin all the time. But in my opinion, this would bring unreasonable extra complications.
By registering you mean that... I will need to one by one add them back to the list of repositories OR after unistalling the older version information about configuration will still remain somewhere and I will just need to go to administration page, click a link to reindex all repositories back again?
A BIG pain I would say.
A possible workaround would be:
1. Export your current repository configuration from the JIRA regular database to a CSV file and then
2. import it into the H2 internal database by using the web console and the import CSV feature.
Depending on you ability to work with databases this could also be a pain.
IMHO, it requires some few commands, hence it should not be too much difficult. I may help you with the 2nd step if you want.
I am able to download it
0.10.13JIRA 5.1 - 6.1.4
It is the standard, Atlassian made Subversion plugin, but I need the Pablo Beltran's "Subversion Plus" plugin (pbeltranl-jira-subversion-plugin-4.0.4), whitch is give more functions and includes an SVN browser.
I downloaded it at the end of september, but now it's disappeared.
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!
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