We have a FishEye instance that is only used for one project (to access an SVN server) and has a limited set of users. For many other projects, we use Stash. These non-FishEye projects show various FishEye errors on the Source tab that are not relevant on the Stash-hosted projects.
How do I make those errors go away, or at least hide them? I don't want to disable Developer Tools completely because I need Stash support, but I don't see a way to limit when FishEye shows up.
I have done this, but there are still references to Fisheye in various places in the project even though I've not established a Fisheye link to this project. The Stash references work, but there are additional Fisheye references that show empty lists.
On the project level adminstration page, at the bottom you will see a section for repository and application links. For your Fisheye dependancy, assign an application link to your fisheye instance and on the other ones assign a specific stash link.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
At the American Academy of Family Physicians, siloed marketing teams faced delays and duplicate work. Kerrie Gottschalk shook things up by moving the department to Jira, streamlining processes, boosting visibility, and sparking stronger collaboration.
Read the story
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.