We are using 30 day trail version for testing before purchasing the product.
But still could not get fisheye work with Jira.
We keep the code separatly in a server that runs gitlab
Um, if you want any help, you're going to need to give us more information.
"could not get fisheye to work with jira" is a bit like telling a car mechanic "my car won't go" - you have not given him anything to look at, and he needs to know if you're low on petrol, the car won't start when you turn the key, the car is in a ditch, or it's being mobbed by a horde of rampaging penguins. He can't begin to guess what to fix when you haven't told him anything about the problem.
You're now asking specific questions without giving us any context.
What have you set up so far? Give us a rough idea of the servers you've got, the servers you have set up and maybe what documentation you have read.
One thing though, based on the way you are asking questions, I have a feeling you have not understood the basic documentation. I humbly apologise if this is incorrect. If you have misunderstood in the way I think you might have, then my explanation is:
Jira is a service that tracks issues. Fisheye is a service that provides a repository viewer for looking at source code. It is possible to get the two to exchange information (Fisheye data shows in places in Jira when it's relevant for example), via plugins you install in Jira. But you have to have a Fisheye service running in order to tell Jira to read it
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs