Is there a way to include Subversion commit information in a search? In the issue navigator? (Last commit? Last revision?)
Subversion Plus has finally become totally free and it can do it. For people interested in traceability JIRA-Subversion there are even more good news: you can see issues on the commit graphs. In other words, track how the JIRA issues are impacting (and driving) your changes and do it in a visual way...
https://marketplace.atlassian.com/1211642
PS: Subversion Plus bundles an enhanced version of the Atlassian JIRA Subversion plugin.
Hi,
We are using Subversion Plus but I do not see how I can add this information to the navigator.
Ideally we would like to programmatically update a custom field with the most recent commit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What version? Plus (4.x) or ALM (5.x).
Subversion Plus was renamed to Subversion ALM and the JQL functions are avilable from the 5.x version (ALM).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Subversion Plus has become public again (with a lot of cheaper pricing).
For sure, it it provides the data what you are looking for.
https://marketplace.atlassian.com/plugins/com.kintosoft.jira.subversion-plus
In the later versions, a calandar view for commits on issues has been supported.
Now, you can create a JQL query for a getting the commits on project or something else, save it as filter on JIRA and create a Subversion Plus calendar view on it. In that way, by opening the view you could see not only the latest commit, even the full commit history.
Something similar to this:
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The next generation of Subversion Plus will support it and almost all the queries someone could imagine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The latest pages of this document
http://issuu.com/kintosoft/docs/subversion_plus
provide detailed information about the new JQL functions supported in the 5.0 version (which is pending Atlassian approval) for searching issues based on Subversion attributes like a revision range, date range, author, comment, file and directories and many more....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Subversion 5.1.0 has just been released:
https://marketplace.atlassian.com/plugins/com.kintosoft.jira.subversion-plus
If you are interested in how it resolves your requirement, register your existing repositories and type in the Issue Advanced Search the following JQL query:
issue in svnCommitDateRange("","","",1)
Parameter meaning:
#1: all the repositories
#2: from date
#3: to date
#4: limits the result to 1 issue (internally the commits are sorted by date in descentant order)
The query above will provide just what you are looking for.
You migh also want to use
issue in svnCommitDateRange()
which returns all the issues related to any commit (although I would recommend you use some filter if you have a lot of issues related to commits)
Save it and create a new Commit Calendar Report to display the results on a calendar view. You can click on the commits in the calendar to see the issues and more details. In that way you would get the commits sorted by date in a visual way rather the latest one only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Humm, do you mean a pure Subversion browser trough JQL?
When you say
Last commit?
what it means?
a) Last commit on Subversion? or
b) Last commit on Subversion related to an issue.
They might differ: for example, an user may relate the TEST-25 issue with the latest commit (r234/HEAD). After, an user might create a new commit on Subversion (r235/HEAD) but not related to any JIRA issue:
By using JQL, you might get the TEST-25 issue which would implicitely be related to the latest (higher) r234 commit . But getting the r235 (the HEAD) would not be possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not possible. You might be able to do it with extra coding, maybe outside of the subversion plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.