Howto force FishEye - Jira link

Wouter de Vries November 17, 2013

We have local instances of JIRA Agile and FishEye/Crucible. For our source code we have a single repository that hosts many projects. I initially setup FishEye with just a single repository and set relative paths in the FishEye configuration. This seems to mess up things because both FishEye and Crucible also watch the root level.

So I removed the single repository and replaced it with a relative repository per project. However this still does not fix the issue, some projects have unrelated commits in the source tab, other projects no commits.

2 answers

1 accepted

0 votes
Answer accepted
Wouter de Vries November 19, 2013

Okay I found out why the source link didn't work correctly. I had not set the 'Repository path' correctly in the project settings in Jira.

0 votes
Nick
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 19, 2013

Commits are related to JIRA issues via the convention of adding an issue key in the commit message.

When JIRA renders the Commits tab for an issue, it asks FishEye for all commits containing the issue key of the issue, across all repositories in FishEye. You can use Project Links in JIRA to restrict the search in FishEye to a specific repository however.

Suggest an answer

Log in or Sign up to answer