Mercurial + Jira + Fisheye -> learnings?

[Angel Ezquerra]

On Sat, Dec 15, 2012 at 11:35 PM, Peter Toft <pto at linuxbog.dk> wrote:
> Thanx  - which kind of interface do you have from Mercurial to FishEye?
>
> I could not get a file link to work while testing yesterday e.g.
> /opt/mercurial_root
>
> After starting "hg serve" and entering the http address to FishEye it worked
> fine though.
>
> /pto
>
>
>
> Den 2012-12-14 23:39, Anteru skrev:
>
> Yes, we're using exactly this combination, and it works very fine so far
> for us.
>
> Cheers,
>   -a
>
> Am 14.12.2012 23:10, schrieb Peter Toft:
>
> Hi again I have been using Jira [1] quite a bit recently for
> ticket-handling, and I can see that it can be integrated with Mercurial
> using FishEye [2]. Anyone of you already using this combo? If yes, I am very
> interested to hear whether is is hot or not :-) Best Peter
>
>
>
> --
> Peter Toft, PhD
> http://petertoft.dk

We use Jira at work and we have FishEye installed. I must say that I
find it a little disappointing, specially when you compare it with the
excellent Bitbucket which is also an Atlassian product.

In my opinion the integration between Jira and FishEye, as far as I
can tell, is very, very weak. They barely know about each other,
starting from the fact that each runs on its own web server, on its
own port. You do not even have a link to go from one to the other from
most pages!

Now, I don't think it is all bad. I like the interface and the product
itself is far from being terrible or unusable. The problem is that it
is just OK when it should and could be so much better. They just need
to copy their own product, bitbucket, and they'd have an amazing
product, IMHO.

Also, I find that the code review process that they propose as a fine
interface but that the process itself is a bit clunky. I don't think
that is really because of FishEye itself, but because I do not like
the "review after push" workflow that you must follow to use FishEye.

Finally, I believe that the most important link is not from the issue
tracker to the source code repository, but from the source code
repository to the issue tracker. You do not need FishEye for that.
Just configure TortoiseHg properly, if that is what you use (to get
links from issue references in commit messages to Jira) and then
configure Jira (setting up smart commit actions) and you are done.

Those are my 2 cents. I hope this helps!

Angel