We are using fisheye and jira and have connected them with an app-link. When a user now clicks on a source-tab for a projekt which is not referenced with a fisheye-repo (in the jira-fisheye-configuration: (http://<jira-url>/secure/admin/ViewFishEyeConfig.jspa), a 403 is displayed, because jira is searching all fisheye-repos for the current jira-issue.
For us, not every user has access to every repo, so that a 403 is occured.
A solution could be, that the Source-Tab is only been disabled for every project which is not referenced in the jira-fisheye-configuration (http://<jira-url>/secure/admin/ViewFishEyeConfig.jspa).
I don't find this feature. Isn't is possible? Is there any other way to prevent this 403 (except disabling the plugin or the app-link)?
If I correctly understood your question, I believe you can only set a different Permission Scheme for a project which has no Fisheye repository. Then, remove the "View Issue Source Tab" ability for everyone on it.
thanks for your answer. Of course this will solve my problem, but we are using the subversion-plugin aswell. So this will disable both, the subversion- and the source-tab.
Also I must search every project for a fisheye-repository.
Atlassian has contacted me. Maybe my problem will be solved with the newest fisheye-version. We will update this month. After that I'm going to report the result.
Thanks for your answer.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs