we are running Jira 5.2 and I installed "Subversion Jira plugin", but I need direction on what to do next. Can anyone point me to documentation on configuring this plugin for jira version 5.2, I would really appreciate it
I do not know which version number you are installing but I am guessing you are using the Atlassian version since you did not state subversion plus or subversion alm.
I need direction on what to do next
If you are using the Alassian's JIRA Subversion plugin, then you have to register your repositories and configure the urls to pointo to an external Subversion web client in order to see the changes.
But maybe you might prefer using Subversion ALM which is simpler to configure as it will install and configure a web client for Subversion on your JIRA instance automatically.
Most of that is useful to know, but we really do need an answer to Pablo's question - *which* Subversion plugin is it. The version is good, but "Jira Subversion plugin" doesn't tell us if it is the Atlassian one or the ALM one (or even another one)
However, if it is one of the two main ones, the documentation for the Atlassian one is rather good, and the docs for the ALM one are even better. Both of them have "historical" links to older stuff, but also the principles haven't really changed, so to get the basics done, you don't need to read older docs - the new ones are more than good enough to get you started.
I think we really do need to know which plugin you're using.
@Adam, the version 0.10.13 unveils you are using the Atlassian's plugin.
In this case you have to talk your JIRA Admins and ask them for configuring the plugin to:
1. Point the urls to your current Subversion web client (ViewVC,..).
2. Register your existing Subversion repositories form the Atlassian plugin
3. Grant developers with the VIEW_DEVELOPMENT_TOOLS (or VIEW_ISSUE_SOURCE_TAB) persmission to see commits from the issue and project tab on JIRA.
ALM would not require extra effort from your admins as the configuration steps would be just the same mentioned above.
However, if your company does not have a webclient for Subversion, then ALM would save a lot of work because your adminis should neither install and configure a new server nor keep it aligned with the JIRA configuration (all the Subversion servers registered on JIRA must also be registered on the 3rd party web client).
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot