Plug in works great and is a major improvement over the JIRA CVS log parsing (esp when the commit logs get really big).

One thing that is a problem is when no commit is found for a issue the "Fisheye" tab is simply blank leading user to wonder.  If no commit is found it would be better to indicate that with text such as "No commits have yet been performed on this issue."

Thanks 

Brendan,

 Nice work, much better scaling for CVS. I did the plugin for mercurial based on the subversion plugin.  I thought that all commits with the Jira issue id in the commit message are referred to in both the CVS and Subversion integration, so that they also show changes on branches, or am I recalling that incorrectly?

~Matt

Mercurial's pretty good. I used it with Xen and it has enough features to be used for version control of a commercial product. There are still some rough edges and it's not always clear why commits for merges are necessary. Branching isn't there yet really - just clone the repository. Merging repositories is hard too.

 ~Matt

Thanks for getting a 3.7 version out so quickly.

Hi, I have created a patch for the fisheye-jira-plugin-0.8 to enable it to use Http basic authentication. We needed this as our fisheye instance is running behind an apache server that requires basic authentication as well as the actual fisheye login (we're using a custom fisheye authenticator for that)

Like the fisheye username and password it requires two (optional) parameters in the fisheye-jira-plugin.properties file an example of these would be:

fisheye.httpbasicauth.username=theusername
fisheye.httpbasicauth.password=thepassword

It is a fairly minor change and hopefully it will be useful. I've added the patch file to a Jira issue here:

http://developer.atlassian.com/jira/browse/FISH-23

Richard King

The 0.8 version is working nicely for me with Jira 3.5.1. Are there any bugs fixed in 0.9 that aren't also fixed in 0.8?

Thanks for a great plugin! My recommendation to customers from now on will be that if they already have FishEye and Jira, then use this "FishEye for Jira" plugin for better response times, a lower load on their CVS or SVN servers, and you even get the source code.

There's a post about this plugin at http://toolsmiths.blogspot.com/2007/07/useful-fisheye-for-jira-plugin.html

~Matt

I've just started using this plugin, and so far it seems to offer alot of functionality which is wonderful.

The plugin only performs queries for changes that contain the project key in the commit log. Given that my project is just now starting to evaluate JIRA, there are no commit logs referencing the newly created project key.

It seems then, that "There were no changes on this branch in the last 10 days." is misleading then. What this message really means is that there were no changes with any references to JIRA project keys. In reality, there have been many commits but they will not show up at all in the JIRA Fisheye plugin view.

Question: Can this be changed so that the query to the fisheye repo will display all commits regardless of whether or not the comments refer to a JIRA issue? 

Guys,

Any troubleshooting tips for getting no responce back from Fisheye? Ive just instaleld the plugin on the latest version of Jira. Here is my responce back from Fisheye:

08-05-06 13:08:10,321 TP-Processor3 DEBUG \[ext.fisheye.projecttabpanel.CrucibleProjectTabPanel\] crucible integration is enabled = true
2008-05-06 13:08:10,322 TP-Processor3 DEBUG \[ext.fisheye.projecttabpanel.CrucibleProjectTabPanel\] has perms to show CRU project panel = true
2008-05-06 13:08:10,322 TP-Processor3 DEBUG \[ext.fisheye.projecttabpanel.CrucibleProjectTabPanel\] FE manager has valid config = true
2008-05-06 13:08:10,324 TP-Processor3 DEBUG \[jira.ext.fisheye.ChangeSetManagerImpl\] searching the following reps for project 'EXPRESS' = {Express}
2008-05-06 13:08:10,325 TP-Processor3 DEBUG \[ext.fisheye.rest.FishEyeRestApiManagerImpl\]         Query URI: http://ipgpocappw012/fisheye/api/rest/query
2008-05-06 13:08:10,325 TP-Processor3 DEBUG \[ext.fisheye.rest.FishEyeRestApiManagerImpl\]            Params: auth="test:7:c28fa9bb88d00f0c5fe50b2a16e0c50f", rep="Express", query="select revisions from dir / where comment =\~ '(^\|\[^a-zA-Z0-9\])EXPRESS-\[0-9\]+($\|\[^a-zA-Z0-9\])' and date > 2008-04-06T03:08:10Z order by date group by changeset return csid",
2008-05-06 13:08:10,340 TP-Processor3 WARN \[apache.commons.httpclient.HttpMethodBase\] Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.
2008-05-06 13:08:10,340 TP-Processor3 DEBUG \[ext.fisheye.rest.FishEyeRestApiManagerImpl\] Response: <response></response>

It is fairly clear the API works too, eg http://myserver/fisheye/api/rest/repositories returns a listing of the repos I have setup. Things I have done. Tried both ways of setting it up (Made fisheye have a trusted application, and doing a username/password method). Both return a blank responce.

Its also picking up the repo name because when I "Mapp repos" it picks up the one I have there called express.

Any ideas?

This announcement affects users who are currently running JIRA, FishEye & Perforce.

Hi folks!

For the last few weeks Atlassian has been working hard on transferring the JIRA Perforce plugin's existing functionality into the JIRA FishEye plugin.

We're pleased to announce that we've finished testing and reached a stage where we're ready to release it in beta! You can access the distribution at:

http://confluence.atlassian.com/display/JIRAEXT/Jira+FishEye+Plugin+-+Perforce+Integration+Beta

or http://confluence.atlassian.com/x/OgBSCQ

Why a beta release? We've tested the plugin extensively before release, but Atlassian doesn't currently use Perforce in any production capacity. So if you:

• have installation troubles
• find any bugs
• can suggest an improvement
• would like a new feature

we'd love to hear from you. Please create an issue at http://developer.atlassian.com/jira/browse/FISH and set the Affects Version/s field to 'Perforce-Beta-0.3'.

Thanks for your help in trying out this new plugin release, we are eager to get your feedback. Further queries can be directed to tim@atlassian.com

cheers,
Tim Pettersen

Similar question to Neil's above, although I believe for Neil the answer is that this replaces the Perforce issue tab panel, as well as the Create Perforce job custom field. Instead of querying perforce directly for files in changelists related to Jobs, it just asks Fisheye.

My question is, what is the recommended upgrade strategy from the perforce plugin to this... Is it to associate the new job custom field with every project that had the old one, and then disable the perforce plugin? Which is fine, except we just spent a grand on that

cheers, jamie

Next question... Project Panels for Fisheye and Crucible. They don't work for us. They appear to do a query on the issue key appearing in the changelog:

2008-05-21 14:03:17,093 INFO [btpool0-24] fisheye.perf BaseQueryEvaluator-performQuery - qlsearch: inmem q=And(TermLookup(EntityClass[11] > EntityClass[120], , null), And(RegEx(EntityClass[10],EntityClass[104],(^|[^a-zA-Z0-9])DTT[0-9]+($|[^a-zA-Z0-9])), AnyLongRange(EntityClass[103],1208782997000, false, 9223372036854775807, true))) in 0ms

We don't associate changelists with issues like this, we use perforce jobs. These are the reasons we use jobs:

• less susceptible to typos, you pick from a list rather than type in some key
• fixes are recorded across integrations, (p4 fixes -i), not so for comments
• jobs allow you to further refine the process if required (eg cannot checkin against a job not assigned to you)

Could this be changed so it queries against related jobs (possibly as well as comments)?

Note: Edwin (Atlassian's head tech writer) and I just sat down and pruned out a few of the older comments on this page relating that related to resolved issues or were deemed to have little purpose.

This may happen from time to time as the length of these threads become too much for what is primarily a documentation page.

For support, please raise issues at http://support.atlassian.com in the FishEye project. For bug reports or feature requests, please raise issue at http://developer.atlassian.com/jira in the JIRA FishEye Plugin project.

I just installed the latest version from http://svn.atlassian.com/svn/public/contrib/jira/jira-fisheye-plugin/tags/jira-fisheye-plugin-1.5. However, the create job custom field has gone, eg all this stuff from the xml file:

<customfield-type key="jobcheckbox" name="Job Checkbox"

Is 1.5 not the version after jira-fisheye-plugin-p4-beta-0.4? How do I get the p4 stuff back?

cheers, jamie

What happens if the user changes their commit message after their original commit? We're using Subversion for our source repository. It appears that the plugin does not recognize or pick up the changed commit message.

Here's the scenario reported to me from one of my users:

The original commit message was:

JIRA-1 - initial commit message

The changed commit is:

JIRA-1 - initial commit message; JIRA-2 : Fixed another problem

The user was expecting to see the list of changed files in both JIRA-1 and JIRA-2.

If the current version of the plugin does not support a changed commit message, would it be possible to support this behavior if I opened a support request?

Hi Jeff,

Normally, the JIRA FishEye plugin caches changeset data resolved from FishEye, in order to speed up the rendering of the issue and project tab panels.

Since version 1.5 there are a couple of easy ways to short circuit this behaviour:

If you wish to refresh the cache (after a commit message has been updated, for example) navigate to the FishEye Configuration view page and click the small Statistics link next to Revision Cache Size. Then press the Flush Cache button.

If you wish to prevent changesets from being cached at all (by retrieving data fresh from FishEye every time), navigate to the FishEye Configuration edit page and set the Revision Cache Size to 0. The potential trade-off is more load on the FishEye instance and your network.

If you are running a version of the JIRA FishEye plugin prior to 1.5, an ad hoc method of flushing the cache is to restart JIRA. No changeset data is persisted over a restart.

cheers,
Tim

The "p4package" that is required for the new plugin... I'm not using Perforce, should I still upgrade?

Perforce support is very broken when using Fisheye plugin with the AppLinks plugin, there is no way to map a project to a perforce path anymore. And the AppLinks plugin can map a project with FishEye, but it also does not know that in perforce different project just reside at different paths ... and there is no such concept in FishEye as a different path in perforce for a single server, just a server. This is SO frustrating.

Hi,

 The machine running jira does not have a direct connection to the one running fisheye, it needs to be done trough a proxy, is it possible to configure such a thing for the plugin?

 muanis

New to Fisheye, I'm looking at the latest release, 2.2, the install docs stop at 1.1, referring to a properties file that isn't in the 2.2 zip. Is it needed in 2.2? is the 2.2 plugin compatible with Jira 3.13?

Previously when I looked at just the perforce plugin there was a perforce-jira-plugin.properties, is this still needed?
cheers!

rg.picocontainer.defaults.UnsatisfiableDependenciesException: com.atlassian.jir
a.ext.fisheye.config.RefreshManager doesn't have any satisfiable constructors. U
nsatisfiable dependencies: [[interface com.atlassian.jira.ext.fisheye.ChangeSetM
anager, interface com.atlassian.jira.ext.fisheye.config.FishEyeConfig, interface
com.atlassian.jira.ext.fisheye.config.FishEyeInstanceStore, interface com.atlas
sian.jira.ext.fisheye.config.RepositoryPathStore, interface com.atlassian.jira.e
xt.fisheye.perforce.PerforceConfig, interface com.atlassian.jira.ext.fisheye.per
force.PerforceManager, interface com.atlassian.jira.ext.fisheye.config.CustomQue
ryStore, interface com.atlassian.jira.ext.fisheye.config.FishEyeRepositoryStore,
interface com.atlassian.jira.ext.fisheye.FishEyeManager]]
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.getGr
eediestSatisifableConstructor(ConstructorInjectionComponentAdapter.java:138)

Anyone else seeing this?