How many licences required for FishEye with Git integration?

[tomisaacson]

We're already using Jira. If we just want to setup FishEye to look at Git so we can see code changes in Jira do we only need one FishEye licence, or do we need multiple licences for every developer?

What about in the future if we wanted to add Crucible? Obviously we need a licence for every developer using that, but do we need to extend the number of FishEye licences?

Thanks.

[Nick · Accepted solution]

Hi Tom,

It depends how open your source code is. If all your developers are allowed to see all the source code, then you should be able to use a 10 user (note: this is different to the 10 committer starter license) license with Basic Auth. This is unrecommended however, since the same single user is used to authenticate all requests from JIRA to FishEye. The recommended and best approach is to use OAuth to authenticate and this requires an account on FishEye for each user wishing to view source from JIRA.

Cheers,

Nick

[tomisaacson]

Can you explain "the same single user is used to authenticate all requests from JIRA to FishEye"? I thought Jira would just be asking about changes per issue, is there more to it?

[Nick]

Hi Tom - when you use Basic Auth between JIRA and FishEye, then the request is made with the context of the user you've configured in the Basic Auth section of the Application Link. JIRA still does ask about changes per issue, however these changes may be in one or more repositories which may be protected for certain users. Using Basic Auth will use the credentials of the user you've configured rather than the context of the user currently logged in to JIRA. I suggest you try this out yourself to see how it works.

[Adam Wride]

Tom - 

If you want to see code changes from Git in JIRA - you could use the Git Integration add-on: https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/