Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

FishEye smart commit messages don't link to JIRA properly?

We have FishEye and JIRA running on the same server on our local lan. In the email messages from both:

FishEye emails contain links in the format: http://hostname:8060/path/to/code

JIRA emails contain links in the format: http://ipaddress:8484/browse/ticket

Not sure why they are different, but they both work at least. The problem is FishEye emails containing JIRA tickets via smart commit tags like #resolve. The FishEye links work but the links to the JIRA ticket are in the format: http://localhost:8484/browse/ticket

Naturally clicking that link attempts to browse your personal computer instead of the JIRA server. Basically all the links work in the screenshot except SUR-1239 which goes to localhost. Any idea what's up, do I have something configured wrong in JIRA and/or FishEye?

3 answers

1 accepted

1 vote
Answer accepted

I would check your application links in Jira and Fisheye. One most likely is set incorrectly to localhost and needs to be set to hostname or ip address. It might be your base url in Jira, but I doubt that if related or duplicate links work from remote machines.

Under Application Links in JIRA:

Applicaiton URL (which can't be changed) is: http://localhost:8060

Display URL (which can be changed) is: http://hostname:8060


Clicking FishEye Configuration on that application link:

FishEye URL (can't be changed): http://hostname:8060/

RPC URL (can't be changed): http://localhost:8060/

If I delete the JIRA<-->FishEye application link and readd it can' I force it to only use hostname?

Nick Atlassian Team May 30, 2012

bq. If I delete the JIRA<-->FishEye application link and readd it can' I force it to only use hostname?

When you add the recipricol link back to FishEye, from JIRA, be sure to use the hostname.

The port numbers are different because Jira and Fisheye have their own services.

Yeah the port part I knew, it's how Atlassian is choosing between hostname/ipaddress/localhost that is confusing

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you