Fisheye/Crucible integration into JIRA and licenses.

[lance_lyons]

I am trying to find out how the Jira integration works for Crucible/Fisheye in terms of licenses.

We have 25 licenses of each crucible and fisheye. We have it integrated in with Jira where we have 100 users. I only have 20 or so developers that will actually use crucible and fisheye for sifting through code.

However I have 30-40 Jira users that may want to see the diff in Jira under source tab. Normally they use tortoise svn to do this but since its integrated into Jira that is the best place.

Is there only 25 of our Jira users that can see the diff from the fisheye integration?

Are all of my Jira users able to see the source tab and checkins? Are they able to see the diffs?

[Felipe Kraemer]

Hi Lance,

As you have more users in JIRA than you have in FishEye/Crucible and all users in JIRA side must see the source code in the JIRA issue, you need to use Basic Authentication only in the Application Link.

• Trusted Applications requires the same user base in both applications.
• OAuth will require an authentication. A message like this will be displayed in the Source tab:
  Server <FishEye_server_name> requires authentication. Login & Approve to view source. Alternatively, hide this message.
• Basic Authentication uses only one administrator account to authenticate in FishEye side for all your users in JIRA side.

If you face any problems, don't hesitate to open a Support ticket.