Will Atlassian Access work/connect to our Hosting of Crucible n Fisheye?

[Brian Paulick]

We are currently hosting an environment containing Jira and Crucible/Fisheye connected to Crowd for authentication. When we migrate our Jira instance to the Cloud and we still would like to use our Active Directory for authentication into Jira, would we have to purchase Atlassian Access or could we switch to JIRA internal user accounts for authentication and not purchase Atlassian Access?

How does the interface connection between a Cloud Jira instance and a hosted Crucible/Fisheye work since Crucible/Fisheye will not be moving to the cloud?

Could we still use our hosted Crowd instance for authentication into Crucible/Fisheye? For how long? Is there a path to migration path to get those Crowd Users and Users Groups who are configured for access into Crucible/Fisheye?

Thanks

Brian

[Gonchik Tsymzhitov · Accepted solution]

Hi @Brian Paulick , 

Atlassian access is available only for Cloud products. It works only for Jira Software, Jira Service Desk, Jira Core, Confluence, and Bitbucket Cloud.

[Alex Fox]

We're facing a similar dilemma. The majority of our infrastructure is moving to the Cloud but for the interim, we will need to maintain an on-prem FishEye/Crucible integrated with Cloud Jira (we're hosting ours in GCP).

You can link Cloud Jira to FishEye/Crucible with an application link and you'll see all the relevant development information, you can also use triggers in workflows based on Crucible events (but not conditions or validators). I believe Automation works with Crucible.

With regard to the authentication question, I believe you'll effectively need to have two authentication solutions, Crowd and Access. Just make sure that the server username matches the Cloud username/email address to properly link code reviews in Crucible with Cloud Jira.