要約

Getting a "The specified FishEye repository is not configured" message when trying to add the FishEye Recent Changesets gadget to a Jira dashboard.

環境

• Fisheye/Crucible and Jira successfully connected using Application Links.

診断

The FishEye Recent Changesets gadget is trying to find the repository inside the repository list cache in Jira before reaching out to Fisheye/Crucible to scan the changesets. In order to check what are the repositories that have been cached follow the steps below:

1. Access Jira from a web browser.
2. Visit the Jira admin > Applications > Integrations > FishEye page.
3. Look for the repository under the "FishEye/Crucible entity mappings" section.

The gadget configuration will fail if the repository is not listed there. There are quite a few different reasons why a repository wouldn't show up inside the list, and we'll go over them in more detail.

原因 1

It is the first time the user is trying to configure that gadget after linking Jira to Fisheye/Crucible using Application Links and the repository list cache was never populated.

原因 2

The user has already tried refreshing the cache mentioned in Cause 1 and yet the list of repositories is not getting populated inside the Jira admin > Applications > Integrations > FishEye page. This can happen when the Application Links were created using OAuth (impersonation) but usernames between Jira and Fisheye/Crucible don't match.

For example, in Fisheye/Crucible my username is admin while in Jira my username is administrator. I may have all the access I need to those repositories in Fisheye/Crucible but because the Application Links are using OAuth (impersonation) the request going out from Jira is made on behalf of administrator when I try to refresh the cache and that user does not exist in Fisheye/Crucible, only admin.

1. Review the Application Link inside both applications: Jira and Fisheye/Crucible.
2. Check if the username of the person trying to refresh the cache matches in both applications.

原因 3

The user has already tried refreshing the cache mentioned in Cause 1 and yet the list of repositories is not getting populated inside the Jira admin > Applications > Integrations > FishEye page. This can happen when the Application Links were created using OAuth but no OAuth token was created for the user trying to refresh the repository list cache yet. In order to verify whether an OAuth token has been created for that user follow the steps below:

1. Access Fisheye/Crucible from a web browser as the user trying to refresh the repository list cache in Jira.
2. Click the Profile icon > Profile settings.
3. The profile settings window will open, go to the Authorized Applications tab.
   1. If there's a message "No applications are using your account to access FishEye data" it means no OAuth token was created for that user yet.
   2. If there are OAuth tokens there review each one of them to make sure there's none from that particular Jira instance you're trying to add the FishEye Recent Changesets gadget to.

原因 4

The user trying to refresh the repository list cache inside the Jira admin > Applications > Integrations > FishEye page doesn't have permissions to the repository in Fisheye/Crucible.

ソリューション 1

Click the "Refresh" button right next to the Global configuration section. The entire page will refresh as well and the repository will start showing up inside the list of cached repositories. The FishEye Recent Changesets gadget will no longer display the "The specified FishEye repository is not configured" message.

ソリューション 2

If the username of the person trying to refresh the repository list cache doesn't match between Jira and Fisheye/Crucible choose from one of the following:

• Update your Application Link configuration to start using OAuth instead of OAuth (impersonation). This will allow the user to authenticate and generate an OAuth token. Usernames don't have to match when using OAuth since the application will start using the OAuth token to make requests on behalf of that user to the other application.
• Rename the user from Jira or Fisheye/Crucible to make sure the usernames match between applications when having the Application Link set up to use OAuth (impersonation).

Once this has been sorted out, go back to the Jira admin > Applications > Integrations > FishEye page and click the "Refresh" button right next to the Global configuration section. The entire page will refresh as well and the repository will start showing up inside the list of cached repositories. The FishEye Recent Changesets gadget will no longer display the "The specified FishEye repository is not configured" message.

ソリューション 3

Ask the user trying to refresh the repository list cache to generate an OAuth token. Here's one way of generating the OAuth token:

1. Access Jira from a web browser as the user trying to refresh the repository list cache.
2. Click the Profile icon > Profile.
3. Find the Activity Stream section.
4. There will be a warning message there with the following:
   1. Additional information may be available, please authenticate for more information:
      • Authenticate with <YOUR_FECRU_INSTANCE_NAME>.
5. Click the Authenticate link.
6. You'll be forwarded to Fisheye and may have to log in if you aren't logged in already.
7. Click Allow to grant your Jira user read and write access to your data on Fisheye/Crucible.

Once the OAuth token has been successfully created, go back to the Jira admin > Applications > Integrations > FishEye page and click the "Refresh" button right next to the Global configuration section. The entire page will refresh as well and the repository will start showing up inside the list of cached repositories. The FishEye Recent Changesets gadget will no longer display the "The specified FishEye repository is not configured" message.

ソリューション 4

Check permissions inside the Fisheye/Crucible repository following these steps:

1. Access Fisheye/Crucible from a web browser.
2. Go to the Fisheye admin > Repository Settings > Repositories page.
3. Find the repository the user is trying to add to the FishEye Recent Changesets gadget in Jira in the list of repositories.
4. Click on the repository name to open the repository settings window.
5. Click on the Permissions tab.
6. Review the permissions on that page and the default repository access permissions page to ensure the user has Read access to the repository.

Once permissions have been sorted out, go back to the Jira admin > Applications > Integrations > FishEye page and click the "Refresh" button right next to the Global configuration section. The entire page will refresh as well and the repository will start showing up inside the list of cached repositories. The FishEye Recent Changesets gadget will no longer display the "The specified FishEye repository is not configured" message.