Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-5731

No entity exists with key ${helper.project.key} of type com.atlassian.applinks.api.application.fecru.FishEyeCrucibleProjectEntityType

      How to reproduce the issue:

      1. Access the Crucible admin section by only inserting the master / root password (by accessing http://HOST:PORT/admin/login-default.do)
      2. Go to Admin >> Project Settings >> Projects >> <choose the project> >> Click on "Application Links" link
      3. The message is displayed:
        No entity exists with key ${helper.project.key} of type com.atlassian.applinks.api.application.fecru.FishEyeCrucibleProjectEntityType 
        

      This message, however, does not say what is really going on.
      To solve the problem, the user must be logged in with an admin user (by accessing http://HOST:PORT/login?origUrl=/).

      I believe that this error could provide more details, or that maybe this screen should enforce there's an admin user logged in.

      Please let me know if you need any additional information.

      Thanks a lot,
      Felipe Kraemer
      Atlassian Support

            [CRUC-5731] No entity exists with key ${helper.project.key} of type com.atlassian.applinks.api.application.fecru.FishEyeCrucibleProjectEntityType

            klfoong right. Thats good - thats what we have done. If you can get to that screen, you will see all projects, and all of the links will work

            Geoff Crain (Inactive) added a comment - klfoong right. Thats good - thats what we have done. If you can get to that screen, you will see all projects, and all of the links will work

            Nick added a comment -

            Hi klfoong thanks for the update on how to reproduce this and also updating the affects version to 2.8.2.

            Nick added a comment - Hi klfoong thanks for the update on how to reproduce this and also updating the affects version to 2.8.2.

            Hi npellow,

            is this issue only occurring if you are logged in only as an admin (and have no user login?).

            I can reproduce the error with login user.

            Please confirm exactly the steps you took to reproduce this on 2.8.x.

            Please refer to the following steps to reproduce the error on 2.8.2 (tested reproducible):

            1. Login as a normal admin user
            2. Make sure that your admin user does not have the View review permission for the project
            3. Go to Admin >> Project Settings >> Projects >> <choose the project> >> Click on "Application Links" link

            Foong (Inactive) added a comment - Hi npellow , is this issue only occurring if you are logged in only as an admin (and have no user login?). I can reproduce the error with login user. Please confirm exactly the steps you took to reproduce this on 2.8.x. Please refer to the following steps to reproduce the error on 2.8.2 (tested reproducible): Login as a normal admin user Make sure that your admin user does not have the View review permission for the project Go to Admin >> Project Settings >> Projects >> <choose the project> >> Click on "Application Links" link

            Nick added a comment -

            klfoong is this issue only occurring if you are logged in only as an admin (and have no user login?).

            Please confirm exactly the steps you took to reproduce this on 2.8.x.

            Nick added a comment - klfoong is this issue only occurring if you are logged in only as an admin (and have no user login?). Please confirm exactly the steps you took to reproduce this on 2.8.x.

            I'm reopening this bug as it doesn't seem to be fixed. I cannot give a concrete deadline for its resolution but it's on top of our list.

            I apologize for the frustration, thanks for your patience.

            Sten
            FishEye / Crucible Product Manager

            Sten Pittet (Inactive) added a comment - I'm reopening this bug as it doesn't seem to be fixed. I cannot give a concrete deadline for its resolution but it's on top of our list. I apologize for the frustration, thanks for your patience. Sten FishEye / Crucible Product Manager

            Same problem (2.7.13) but also see https://jira.atlassian.com/browse/FE-4087 where all our previously happy users are now being blocked from access to their projects. These two issues must be related. Had to allow anon 'View' access to Permission Scheme for my people to get into their CRU projects.

            Please raise the priority of this issue!

            Thank you

            Craig Solinski added a comment - Same problem (2.7.13) but also see https://jira.atlassian.com/browse/FE-4087 where all our previously happy users are now being blocked from access to their projects. These two issues must be related. Had to allow anon 'View' access to Permission Scheme for my people to get into their CRU projects. Please raise the priority of this issue! Thank you

            Having same issue with Crucible after upgrade from 2.7.12 to 2.7.13. The fisheye integration is working properly while crucible is giving me this error with
            https://host:8446/fecru/plugins/servlet/applinks/listEntityLinks/com.atlassian.applinks.api.application.fecru.FishEyeCrucibleProjectEntityType/$%7Bhelper.project.key%7D

            Does anyone have fix for this issue?

            Thank you.

            Vladimir Omelchenko added a comment - Having same issue with Crucible after upgrade from 2.7.12 to 2.7.13. The fisheye integration is working properly while crucible is giving me this error with https://host:8446/fecru/plugins/servlet/applinks/listEntityLinks/com.atlassian.applinks.api.application.fecru.FishEyeCrucibleProjectEntityType/$%7Bhelper.project.key%7D Does anyone have fix for this issue? Thank you.

            Same issue here with lates version of FishEye

            Ivan Demkovitch added a comment - Same issue here with lates version of FishEye

            Kyle added a comment -

            Hey Guys,

            I have this @ Version:2.7.11 Build:20120227023831 2012-02-27.

            Regards,
            Lee

            Kyle added a comment - Hey Guys, I have this @ Version:2.7.11 Build:20120227023831 2012-02-27. Regards, Lee

            Rafal Habrat added a comment - - edited

            Hi Guys,

            I've been experiencing the same problem. The problem is related to Permission Schemes - I hit this problem when the admin account I was using was not granted the "View" permission for the Crucible projects that used that particular permission scheme. As a result, I was seeing the "No entity exists with key ${helper.project.key} of type com.atlassian.applinks.api.application.fecru.FishEyeCrucibleProjectEntityType" error when I tried clicking on the Application Links.

            My initial workaround was to modify the URL by hand (replacing the ${helper.project.key} with the key of the Crucible project) when trying to set up application links to JIRA - that kind of worked as I was able to configure the link between the JIRA project and the Crucible project but I still did not see the Crucible projects appear in JIRA under Mapped Crucible Projects. I then modified the permission scheme so that the fisheye-admins group had the "View" permission and the error disappeared and in JIRA, the Crucible projects showed up. It seems to me that the code that validates permissions is a bit too strict as it prevents admins from setting up the integration unless they have the View permission and it also affects what is shown in JIRA which is kind of unexpected.

            Hth,
            Rafal

            Rafal Habrat added a comment - - edited Hi Guys, I've been experiencing the same problem. The problem is related to Permission Schemes - I hit this problem when the admin account I was using was not granted the "View" permission for the Crucible projects that used that particular permission scheme. As a result, I was seeing the "No entity exists with key ${helper.project.key} of type com.atlassian.applinks.api.application.fecru.FishEyeCrucibleProjectEntityType" error when I tried clicking on the Application Links. My initial workaround was to modify the URL by hand (replacing the ${helper.project.key} with the key of the Crucible project) when trying to set up application links to JIRA - that kind of worked as I was able to configure the link between the JIRA project and the Crucible project but I still did not see the Crucible projects appear in JIRA under Mapped Crucible Projects. I then modified the permission scheme so that the fisheye-admins group had the "View" permission and the error disappeared and in JIRA, the Crucible projects showed up. It seems to me that the code that validates permissions is a bit too strict as it prevents admins from setting up the integration unless they have the View permission and it also affects what is shown in JIRA which is kind of unexpected. Hth, Rafal

              gcrain Geoff Crain (Inactive)
              fkraemer Felipe Kraemer
              Affected customers:
              5 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: