Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hello,
I have Jira and Fisheye installed and connected together.
I would like to list in Jira (very convenient thanks to the result list view) the bugs that have been fixed since a given SVN revision.
I can get the information in Fisheye but it forces me to switch from Jira to Fisheye, and I can't get the bug summary and other useful information displayed on the same screen.
So I would prefer to request with JQL for instance the informations of the source tab, but can't figure how to do it.
Any clue?
B/R,
Julien
I asked Altassian support and get this answer:
https://support.atlassian.com/browse/JSP-175096
To summarize, it is not doable, and they recommend that we develop the missing function. Maybe, we will give it a try.
Hi Julien,
You can try the Release Report plugin for FishEye. It will let you pick two points of history and have the list of issues that have been committed between those two commits. And for each issue you will be able to see the status (open, closed, etc.).
The screenshot below shows what the results look like. Depending on how many commits have to be processed it might take some time to get the results back but I really encourage you to try it out and give us your feedback. This could help us to refine this project and include this type of reporting into FishEye.
Please don't hesitate to post some feedback on the plugin page.
Regards,
Sten Pittet
FishEye / Crucible Product Manager
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
the release report plugin is a great plugin, but it does not fit our needs. Indeed, we are looking for a way to list the issues fixed by SVN revision, and scan them using the standard JIRA features (which are very efficient from V6)
Moreover Fisheye is way too slow on our instance, and we could not improve that so far.
So the solution proposed in another answer (suppressed it seems), based on Subversion Plus, was better, but way too expensive for this small specific requirement, and not perfect as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you mean... "and not perfect as well"?
Why is not the Subversion Plus solution "perfect" ;) ?
Regarding the pricing, it has been reviewed. I would say now it is even too much cheap, seriously.
https://marketplace.atlassian.com/plugins/com.kintosoft.jira.subversion-plus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you want to see something perfect? Install the latest version and look at the new commit graphs (and ensure that the issue checkbox is checked :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Regarding the pricing... it became totally free!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm aware this question is regarding to Fisheye, anyway you might be interested in having a look at Subversion Plus which can do what you are asking for.
Disclaimer: I'm the author of the add-on and it is commercial, however you might want to see it in action whether you are curious. Selling it is not the most important for me at the moment, I would appreciate a lot any feedback. On the other hand, you could use it for the trial period which can be extended for several months for free. It's not a new add-on, the free version ran (and runs) installed on hundreds of JIRA instances with a lot of lovely feedback. The installation requires one click only (no extra servers nor any other 3rd party soft is required).
Once installed register your repository and run this JQL:
issue in svnCommitNumberRange(<repoId>, <start_commit>, <end_commit>, <limit_issues>)
For example:
issue in svnCommitNumberRange(1, 2345,"", 50)
would return the 50 issues related to the latest commits (newer) on the reporitory id=1 starting by the 2345 revision to HEAD (= end_commit empty)
... and combine it with JIRA attributes filter as usual:
AND status=Open
=================
Extra bonus:
Save the query above as filter and use the Commit Calendar Report to show the commits on a calendar view and see also the % contribution of each Subversion user.
==========
The link to Subversion Plus add-on for JIRA
https://marketplace.atlassian.com/plugins/com.kintosoft.jira.subversion-plus
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.