Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-4178

Getting "No entity exists with key <REPONAME> of type com.atlassian.applinks.api.application.fecru.FishEyeRepositoryEntityType" editing clicking applinks for a repository

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • High
    • 2.7.15
    • 2.7.13
    • Integrations
    • None
    • JDK 1.6.0_29, CentOS 5.8, MySQL 5.5

    Description

      Just today we noticed that clicking the applinks menu option for any repository results in the following error message:

      No entity exists with key appdev of type com.atlassian.applinks.api.application.fecru.FishEyeRepositoryEntityType
      Status code: 400
      

      All of our repositories are restricted by LDAP filters.
      The error only appears for those repositories where I'm not a member of the LDAP group with repository access.
      Given that only Fisheye admins would be able to add applinks, it seems like Fisheye is looking in the wrong place for permissions (repo-view permissions instead of admin permissions)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              b0d88db9bee7 David Corley
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: