Dev Panel shows "commits" from Crucible-Only App Link.

Summary

When connecting JIRA to a Crucible Instance that does not have FishEye Enabled, JIRA shows commits of the Repository configured within Crucible. This causes problems in the development panel, as links to the commits do not work.

Environment

Steps to Reproduce

1. Successfully linking JIRA and FishEye-Crucible, ensuring you can see a Commit in a JIRA Issue
2. Remove the FishEye License from FishEye Crucible.
3. When you try to access the commit from the Branch pop-up, you get a "Project does not Exist" error.

Expected Results

Commits should not be shown if they can not be accessed through FishEye.

Actual Results

The Development Panel shows commits for the repository configured with Crucible, even if a Crucible only app-link is made.

Notes

• This is similar to DCON-342
• We should restrict what is being shown to improve usability of the product.

Workaround

One workaround which will completely hide commits from the Dev Panel, which may not be desired is as follows:

1. Click the Administration Cog and select "Add-Ons".
2. Click Manage add-ons on the left-hand side of the screen.
3. Use the drop-down box in the Manage Add-ons filter to select All add-ons.
4. Locate the Atlassian JIRA - Plugins - Development Integration Plugin and Expand this Add-on
5. Click the 71 of 71 modules enabled link.
6. Locate the devstatus-commits module and click the Disable button.