Repository list cache refresh doesn't work

Hello,

I've got problem with linking JIRA with FishEye. Despite having configured app link to FishEye I don't see all repos from FishEye. I tried to compare repo I see and one I don't but found nothing. Also I can't refresh repository list cache. Button is clickable but date of last refresh doesn't change after clicking at it.

4 answers

Sorry I don't have an answer :-(

I'm using JIRA 6.0.6 and FishEye 3.1.4 and have a similar issue.

In the FishEye plugin config page in JIRA, even after I refresh the repositories cache, a number of repositories still don't show up in the list. The date does update for me but nothing seems to change otherwise. I also don't see any difference in the repositories that show up and the ones that don't.

Hoping someone from Atlassian will answer or I will open a ticket.

Despite having configured app link to FishEye I don't see all repos from FishEye.

Are you able to see the commits which contain a JIRA issue key appearing on the view issue page?

There is no need to map JIRA projects to FishEye repositories in the versions of FishEye and JIRA you are using.

Hi Nick,

What do you mean with "There is no need to map Jira projects to FishEye repositories in the versions of FishEye and JIRA you are using"

Sorry, I thought you may be trying to configure project entity links. These are no longer needed.

Did you fix your problem ?

Thanks for answering!

No I can't see any commits which contain a JIRA issue key on the view issue page source tab.

Concerning the mapping of JIRA projects to FishEye repositories: If I don't map the JIRA project to the FishEye repo, then in the JIRA overall project view source link, I will only see commits containing a project key. If I map the project to the repo, then at project level source link I will see all commits for the repo. Is there some other way to see all of the commits at the project level?

It seems the Application Link functinality really only provides for commits to show up at overall project level if the commit refers to the project. While this makes sense and is a good practice, currently not all of our commits do this.

I take it that if more than one repository has a commit msg that refers to the same JIRA project, both will show up in JIRA project and issue source tab?

Thanks!

This! I have a JIRA project where I only want a specific repo path to show up in the Development Panel regardless of JIRA key in the commit message. (We have customer-specific development branches.) I'm having trouble figuring out how to over-ride the default behavior of JIRA picking up every commit from every repo. Even configuring both a specific Project Link and a Repository Path doesn't over-ride the default behavior.

Hi,

I think that for me it helped adding trusted app and ip patterns in it.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,104 views 13 19
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot