FishEye for JIRA

Version 2.5 Released!

JIRA FishEye Plugin 2.5 has been released - please note that it requires FishEye/Crucible version 1.6.6+ to work correctly.

Perforce Users

Versions 2.2.2, 2.3 and 2.4 of the plugin include a regression that prevents changesets matched using the 'Jobs Fixed' field from being displayed in JIRA. Please upgrade to Version 2.5 if this affects you!

Name JIRA FishEye Plugin
Vendor Atlassian Pty Ltd (Website)
Authors Atlassian
Homepage http://confluence.atlassian.com/display/JIRAEXT/FishEye+for+JIRA
Issue Management http://developer.atlassian.com/jira/browse/FISH
Continuous Integration n/a
Categories Remote Access
Most Recent Version 2.5.2
Availability JIRA v3.13 to v3.13
State Stable
Support Atlassian Supported Plugins
License Freeware / Open Source (BSD)
Price Free
Release Docs http://confluence.atlassian.com/display/JIRAEXT/FishEye+for+JIRA
Java API Docs n/a
Download Source http://svn.atlassian.com/svn/public/contrib/jira/jira-fisheye-plugin/tags/jira-fisheye-plugin-2.5.2
Download JAR jira-fisheye-plugin-2.5.2.zip


"Realtime linking between your source code repository and JIRA"


Welcome to the FishEye for JIRA plugin page. On this page you will find a brief outline of the plugin's functions, screenshots of the plugin in action, links to detailed documentation and other useful resources.

Future Development
Bugs, Feature Requests & Improvements?

If you've found a bug in the JIRA FishEye plugin or would like to request a new feature or improvement - please raise an issue in the JIRA FishEye Plugin project.

Crucible Standalone is Now Supported

If you have JIRA and Crucible without FishEye, you should download and install the latest version of the JIRA FishEye Plugin to link your JIRA issues to your Crucible reviews.

FishEye for JIRA Overview

Relevant information from the repository, right when you need it

Your source code repository contains an abundance of useful information about the life of your software project. FishEye is a web-based tool that takes that information and publishes it to your browser, where you can explore, search, analyse and link anywhere in your project's source. The FishEye plugin for JIRA expands the power of FishEye, by allowing you to see the direct connections between JIRA issues and your source repository.
  • See the changelog for every check-in made against your project in the JIRA project page
  • Analyse development activity, measuring lines of code, files or commits over the past 7, 30, or 90 days
  • View project charts showing commit activity by author or issue
  • See commits made against a specific JIRA issue
  • The Issue Tab panel (screen at left) automatically retrieves changesets that relate to the current JIRA issue (retrieved using the issue key).
  • Changesets from can be expanded and contracted individually for easy viewing.

Link JIRA issues to source files

The FishEye plugin for JIRA automatically and instantly associates individual check-ins with the issues they reference.
  • When you commit a fix for JIRA issue JRA-1234, information about that commit is displayed directly on the JRA-1234 screen.
  • The Project Screen (pictured at left) shows all the changesets from FishEye relating to the current project. This is a combined view of work in progress expressed in meaningful charts, along with links to the most recent changesets from your repository.


View history and chart activity for your JIRA project

Who's committing code? How often? What are they doing? What bugs are causing the most changes? The FishEye plugin for JIRA gives your team a look at your projects' commit history and activity statistics. All data is fetched in real-time to always show the latest information.
  • Ideal for project managers, the Statistics View (image at left) shows an accessible visualisation of the work being done on the selected project in your repository.
  • See activity expressed as files, commits or Lines of Code (LOC).



Customise your dashboard with SCM-related portlets

Create an integrated view of your entire project by adding FishEye portlets to your dashboard!
  • Monitor recent commit activity for a particular project, or an entire repository
  • View changes in LOC over time by project and/or author
  • Break-down your charts by subdirectory, file-type or repository path
Monitor your code quality with Crucible review metrics on your JIRA dashboard.
Available Crucible charts include:
  • Open Reviews
  • Open Review Age
  • Defect Classification
  • Defect Rank
  • Comment Volume

    All charts can be configured by project and most are scalable to a period of your choosing.


Search code repositories, monitor commit activity

From within JIRA, you can easily jump over to FishEye. Within FishEye, you get additional powerful search capabilities that allow you to search over your entire source code repository.
  • You can search by filename, author, date, tags or branches, as well as full-text search of the files themselves.
  • Configurable RSS and email notifications allow the team to stay on top of changes occurring in the source.
  • Link directly back to your repository with automatic references created by the FishEye for JIRA plugin.
  • Access change history, diffs or download source files from FishEye with a single click.
  • FishEye provides many more powerful features.



Future Development
Bugs, Feature Requests & Improvements?

If you've found a bug in the JIRA FishEye plugin or would like to request a new feature or improvement - please raise an issue in the JIRA FishEye Plugin project.

Labels

atlassian-supported atlassian-supported Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. May 19, 2006

    Lehky, Miro says:

    Plug in works great and is a major improvement over the JIRA CVS log parsing (es...

    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 

    1. May 19, 2006

      Brendan Humphreys says:

      Had a few hours to kill in SF waiting for a flight, so have implemented your sug...

      Had a few hours to kill in SF waiting for a flight, so have implemented your suggestion. See version 0.5 above.

      Cheers,
      -Brendan

      1. May 25, 2006

        Lehky, Miro says:

        Thanks...Thats very helpful.  Fixing the sort of the commits was a big help...

        Thanks...Thats very helpful.  Fixing the sort of the commits was a big help.

  2. Nov 08, 2006

    Matt Doar says:

    Brendan,  Nice work, much better scaling for CVS. I did the plugin for mer...

    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

    1. Nov 08, 2006

      Brendan Humphreys says:

      Hi Matt, I have some vague recollection that the CVS or SVN integration didn't ...

      Hi Matt,

      I have some vague recollection that the CVS or SVN integration didn't automatically index commit messages on branches, but I can't find any evidence of it now. It's possible it was a config thing (like specifying an SVN "trunk" project dir, which means branches wouldn't be indexed). I've removed that benefit from the list above.

      Cheers,
      -Brendan
      P.S. what are your experiences with Mercurial?

  3. Nov 08, 2006

    Matt Doar says:

    Mercurial's pretty good. I used it with Xen and it has enough features to be use...

    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

  4. Dec 22, 2006

    Lehky, Miro says:

    Thanks for getting a 3.7 version out so quickly.

    Thanks for getting a 3.7 version out so quickly.

  5. Jan 05, 2007

    Richard King says:

    Hi, I have created a patch for the fisheye-jira-plugin-0.8 to enable it to use H...

    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

  6. Jul 25, 2007

    Matt Doar says:

    The 0.8 version is working nicely for me with Jira 3.5.1. Are there any bugs fix...

    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

  7. Dec 14, 2007

    Seon Lee says:

    I've just started using this plugin, and so far it seems to offer alot of functi...

    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? 

    1. Dec 14, 2007

      Tim Pettersen says:

      Hi Seon! The FishEye Recent Commits portlet should display all changesets under...

      Hi Seon!

      The FishEye Recent Commits portlet should display all changesets under a particular branch, not just those containing issue or project keys in their comments.

      If they're not showing it may be a result of an invalid configuration. Can you double-check that you've specified the correct FishEye branch and repository on the Edit Portlet screen?

      If your config appears fine but it's still not showing recent commits, please raise a support request at http://support.atlassian.com under the FishEye project and we'll help you out.

      cheers,
      Tim

      1. Feb 28, 2008

        Martin Sweitzer says:

        >Question: Can this be changed so that the query to the fisheye repo will dis...

        >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?
        >The FishEye Recent Commits portlet should display all changesets under a particular branch, not just those containing issue or project keys in their comments.

        I believe he is speaking about the FishEye in the Project Tab Panel.  So there definitely should be an option to display all changes there.

         It would also be really great to have FishEye also look for jobs (i.re when using perforce). I have a changelist that I have attached a job to.  That is all that I should need to do.  Having to duplicate the data in the changelist is just painful

      2. Apr 03, 2008

        Rizwan Kassim says:

        To echo Martin's point below : ">Question: Can this be changed so that the q...

        To echo Martin's point below :

        ">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?
        >The FishEye Recent Commits portlet should display all changesets under a particular branch, not just those containing issue or project keys in their comments.

        I believe he is speaking about the FishEye in the Project Tab Panel.  So there definitely should be an option to display all changes there. "

        That would be awesome.  Any chance for this?

        1. Apr 03, 2008

          Tim Pettersen says:

          Absolutely, I've raised a feature request in the FishEye Plugin JIRA project to ...

          Absolutely, I've raised a feature request in the FishEye Plugin JIRA project to implement it.

          Please leave any comments/suggestions on the issue.

          Thanks for the great idea guys!

          cheers,
          Tim

          1. Apr 10, 2008

            Rizwan Kassim says:

            Thanks Tim. Any ideas when this might be done?

            Thanks Tim. Any ideas when this might be done?

            1. Apr 10, 2008

              Tim Pettersen says:

              Hi Rizwan, I've literally just finished implementing this and am testing as I w...

              Hi Rizwan,

              I've literally just finished implementing this and am testing as I write this. It will ship with the 1.5 release of the JIRA FishEye Plugin (in the next week or so).

              cheers,
              Tim

              1. Apr 17, 2008

                Rizwan Kassim says:

                Awesome! Thanks.

                Awesome! Thanks.

  8. May 05, 2008

    Sherif Mansour says:

    Guys, Any troubleshooting tips for getting no responce back from Fisheye? Ive j...

    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?

    1. May 05, 2008

      Tim Pettersen says:

      Hi Sherif, Thanks for the detailed problem description, would you mind raising ...

      Hi Sherif,

      Thanks for the detailed problem description, would you mind raising this as a support request in JIRA FishEye Plugin project?

      In the meantime, lets make sure that it's definitely a problem with the plugin's integration. Try running the following EyeQL query on your Express repository in FishEye (in FishEye, navigate to Search -> Switch to Advanced Search):

      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
      

      Please create a support request with the output from the above query along with the version numbers for the JIRA FishEye plugin, JIRA and FishEye versions you are using.

      cheers,
      Tim

  9. May 12, 2008

    Tim Pettersen says:

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

    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

    1. May 21, 2008

      Neil Arrowsmith says:

      n00b question alert. We don't use Fisheye yet, but as heavy Jira and Perforce us...

      n00b question alert. We don't use Fisheye yet, but as heavy Jira and Perforce users, we are looking into it. The Fisheye/Jira integration would be essential for us.

      I thought that Perforce was supported by Fisheye out of the box, and hence by the Jira integration plug-in. So what does this add, and why is it only Beta?

      Thanks very much
      Neil

      1. May 21, 2008

        Tim Pettersen says:

        Hi Neil, Jamie is correct, the FishEye plugin queries FishEye for changes to yo...

        Hi Neil,

        Jamie is correct, the FishEye plugin queries FishEye for changes to your Perforce repository instead of directly querying Perforce.

        The advantages of the JIRA FishEye plugin over the Perforce plugin are:

        • It's FREE (provided you have a FishEye license)
        • It's bundled with JIRA and has a carefully planned upgrade path, for easier maintenance
        • It contains other nifty FishEye-specific integration features beyond what the Perforce plugin offers e.g. portlets, Crucible integration, project tab panels etc (see the rest of this page) although there is an existing issue relating to these which will be fixed in the next release
        • Dynamic configuration via the UI, instead of the old perforce-jira-plugin.properties file

        The reason it is in a BETA phase is that Atlassian doesn't use Perforce in production capacity. We still thoroughly test it, but simulating real-time use of the plugin is tricky to do accurately. However there should be a final release in the next couple of weeks.

        The upside of being in BETA is that the Perforce integration has a very high priority and I'm constantly monitoring and fixing/implementing bug reports, comments and suggestions - so if you're a JIRA/Perforce/FishEye user and you have any feature requests, now is definitely the time to raise them!

        cheers,
        Tim

        1. May 27, 2008

          Neil Arrowsmith says:

          Thanks Tim I guess I just assumed that, as Fisheye supports Perforce, there was...

          Thanks Tim

          I guess I just assumed that, as Fisheye supports Perforce, there wasn't any issue with Jira connecting to Perforce via the Fisheye Plugin. Does Jira not query Fisheye in an SCM-independent way?

          1. May 27, 2008

            Tim Pettersen says:

            Actually, JIRA's querying of FishEye is almost completely SCM independent. How...

            Actually, JIRA's querying of FishEye is almost completely SCM independent.

            However, when Perforce is used the FishEye plugin queries for changesets based on the criteria of "Jobs fixed" as well as matching JIRA issue/project keys in changeset comments.

            There are also a few other features surrounding Perforce job integration (custom fields, workflows, etc) that have been ported over from the Perforce plugin.

            However, if you don't use Perforce's job integration functionality, you're probably better off using version 1.5 of the plugin for the time being. The beta is really just for testing the integration features regarding Perforce jobs.

            Sorry this wasn't clearer from the start - we've recently fixed FISH-168 to highlight the difference between changes integration and job integration on the interface.

            cheers,
            Tim

  10. May 21, 2008

    Jamie says:

    Similar question to Neil's above, although I believe for Neil the answer is that...

    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

    1. May 21, 2008

      Tim Pettersen says:

      Hi Jamie, Yes - creating a new job custom field and associating it with your JI...

      Hi Jamie,

      Yes - creating a new job custom field and associating it with your JIRA projects is the right way to do it. Once this has been done you should be able to disable the Perforce plugin. I've raised an issue to create some documentation specifically relating to upgrading from the Perforce plugin to the FishEye plugin.

      Regarding your existing Perforce license - our customer advocates are currently working on an incentive scheme for migrating users over to the FishEye plugin as we don't want to hurt customers who have already paid for Perforce plugin maintenance. I'll let you know as soon as more concrete details are available!

      cheers,
      Tim

  11. May 21, 2008

    Jamie says:

    Next question... Project Panels for Fisheye and Crucible. They don't work for us...

    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)?

    1. May 21, 2008

      Tim Pettersen says:

      Absolutely. Actually there's already an issue raised for this in the plugin's JI...

      Absolutely. Actually there's already an issue raised for this in the plugin's JIRA project.

      It will require some work on FishEye itself (project key matching isn't currently possible on the p4jobid field via the exposed FishEye API) which means users will have to upgrade their plugin and FishEye instance once we've implemented this.

      I've scheduled it for the next beta release.

      cheers,
      Tim

      btw thanks for the continuous feedback - keep it coming!

  12. May 27, 2008

    Tim Pettersen says:

    Note: Edwin (Atlassian's head tech writer) and I just sat down and pruned out a ...

    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.

  13. Jun 03, 2008

    Jamie says:

    I just installed the latest version from http://svn.atlassian.com/svn/public/con...

    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

    1. Jun 03, 2008

      Jamie says:

      bah I think I've got confused between the p4 beta 1.5 and this 1.5. You mentione...

      bah I think I've got confused between the p4 beta 1.5 and this 1.5. You mentioned that 1.5 beta of the p4 integration is released, but again it's not tagged in svn, which is prob why I checked out the wrong thing.

      When are you going to merge these two?

      cheers, jamie

      1. Jun 04, 2008

        Tim Pettersen says:

        Hi Jamie, The beta will be rolled into the plugin trunk and released as 1.6 ear...

        Hi Jamie,

        The beta will be rolled into the plugin trunk and released as 1.6 early next week.

        If you want to get in early, version 0.5 of the beta has now been tagged in our public SVN repo: https://svn.atlassian.com/svn/public/contrib/jira/jira-fisheye-plugin/tags/jira-fisheye-plugin-p4-beta-0.5

        cheers,
        Tim

  14. Jun 09, 2008

    Jeff Schnitter says:

    What happens if the user changes their commit message after their original commi...

    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?

  15. Jun 09, 2008

    Tim Pettersen says:

    Hi Jeff, Normally, the JIRA FishEye plugin caches changeset data resolved from ...

    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

  16. Jun 24, 2008

    Dan Morrow says:

    The "p4package" that is required for the new plugin... I'm not using Perforce, s...

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

    1. Jun 24, 2008

      Tim Pettersen says:

      Hi Dan, Yep! You should still upgrade. atlassian-p4package is going to be bun...

      Hi Dan,

      Yep! You should still upgrade.

      atlassian-p4package is going to be bundled with JIRA 4.0. Until then, you'll need to manually copy the JAR into your WEB-INF/lib directory.

      The extra JAR won't cause any problems if you're not using Perforce and there were plenty of non-Perforce related improvements included in the release.

      cheers,
      Tim

  17. Aug 26, 2008

    Evgeny Zislis says:

    Perforce support is very broken when using Fisheye plugin with the AppLinks plug...

    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.

    1. Aug 28, 2008

      Tim Pettersen says:

      Hi Evgeny, May I ask which versions of the FishEye plugin and AppLinks plugins ...

      Hi Evgeny,

      May I ask which versions of the FishEye plugin and AppLinks plugins you are using? I just tested the scenario you described using versions 2.1 (FishEye) and 1.1.2 (AppLinks) and it seemed to work perfectly.

      Steps taken:

      1. Installed the above two plugins
      2. Configured the AppLinks plugin and setup Trusted Applications between my FishEye and JIRA instances
      3. Delegated the FishEye plugin's configuration to AppLinks (clicking on the banner at the top of the FishEye configuration screen)
      4. Specified a Project Path for each of my Perforce projects via the JIRA Administer Project screen. (see screenshot) You can specify a sub-path of a Perforce repository / depot here if you like, e.g. enter /test_project as your path for //depot/test_project.

      Is this similar to what you attempted to do?

      cheers,
      Tim

      1. Aug 28, 2008

        Evgeny Zislis says:

        Looks like I just might have missed it, because it was at the bottom and after I...

        Looks like I just might have missed it, because it was at the bottom and after I tweaked with the AppLinks it changed position. It seems to work now. But AppLinks still does not restrict itself to the repository path. While in the project FishEye tab I see only the commits done to the files of this particular project, and crucible allows to map a cru-project to a jira-project - the only thing left for AppLinks to do is show "just" the commits that fisheye plugin shows. Currently it shows all commits to perforce .. regardless of what path they were sent to.

         I have all the latest versions of all the products and plugins ...

        Thanks for the reply!

        1. Aug 28, 2008

          Tim Pettersen says:

          Hi again Evgeny! There is a method for setting up FishEye repositories so they'...

          Hi again Evgeny!

          There is a method for setting up FishEye repositories so they're related to a particular Perforce path rather than just a depot.

          If you set the PATH attribute on the Add/Edit Repository page in FishEye, FishEye will only scan commits under that particular path. This way you can relate a JIRA Project -> FishEye Repository -> Perforce Project. If you have multiple Perforce projects on the same server - or separate servers for that matter - you can set up a FishEye repository for each one in this manner.

          However, if you'd still prefer the ability to map to a particular path via AppLinks, please raise an issue in the AppLinks project on https://studio.atlassian.com.

          Hope this helps!

          cheers,
          Tim

  18. Sep 05, 2008

    Jose Muanis F. Castro says:

    Hi,  The machine running jira does not have a direct connection to the one...

    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

  19. Sep 19, 2008

    Andy Brook says:

    New to Fisheye, I'm looking at the latest release, 2.2, the install docs stop at...

    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!

    1. Sep 22, 2008

      Tim Pettersen says:

      Hi Andy! Sorry for the delayed reply. 2.2 is indeed compatible with JIRA 3.13 a...

      Hi Andy!

      Sorry for the delayed reply. 2.2 is indeed compatible with JIRA 3.13 and is configured via the JIRA administration web interface - no properties files required!

      cheers,
      Tim

  20. Oct 13, 2008

    Matt Doar says:

    rg.picocontainer.defaults.UnsatisfiableDependenciesException: com.atlassian.jir ...

    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?

    1. Oct 13, 2008

      Tim Pettersen says:

      Hi Matt, That's not good.. which version are you using? Is there any chance t...

      Hi Matt,

      That's not good.. which version are you using?

      Is there any chance that you have either two copies of the FishEye plugin installed or possibly an old version of the Perforce plugin kicking around on your classpath?

      cheers,
      Tim

      1. Oct 14, 2008

        Matt Doar says:

        Yeah, surprised me too. FishEye 1.5.2 and JDK 1.6.x It happened with JIRA 3.12.3...

        Yeah, surprised me too. FishEye 1.5.2 and JDK 1.6.x It happened with JIRA 3.12.3 then again with a brand new copy of 3.13. I guess there must be some old jar somewhere but I couldn't see it.

        ~Matt

        1. Oct 15, 2008

          Matt Doar says:

          Tim, I've filed a more complete issue with Atlassian about this (http://jira.at...

          Tim,

          I've filed a more complete issue with Atlassian about this (http://jira.atlassian.com/browse/JRA-15775)
          Looks like bad data got added to the database by JIRA somehow. It's also the same thing filed at https://support.atlassian.com/browse/FSH-1189?page=com.atlassian.jira.pl by the customer.

          ~Matt

          1. Oct 15, 2008

            Tim Pettersen says:

            Thanks for the tip Matt - I'll respond on the issue. cheers, Tim

            Thanks for the tip Matt - I'll respond on the issue.

            cheers,
            Tim