Create issue from comments on reviews does not work if logged in as regular Crucible user

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Low
    • N/A
    • Affects Version/s: 4.8.9
    • Component/s: Integrations
    • None
    • Severity 2 - Major

      Issue Summary

      When logged in to Crucible as a regular user (no admin), the "Create Issue" dialog displayed after clicking the "Create Issue" link displayed in a comment made on a review (shown when the review has a Linked Issue) does not work. The "Create Issue" dialog just shows a spinning icon indefinitely.

      If logged in to Crucible with an administrator user the "Crete Issue" dialog works just fine.

      Steps to Reproduce

      1. Make sure that the Application Link between Crucible and Jira is fully functional
      2. Log in to Crucible with a regular user
      3. Create a review, making sure to configure a Linked Issue
      4. Browse to a file and add a comment in the diff
      5. Click the "Create Issue" link displayed in the comment:
      6. The "Create Issue" dialog shows up, but a spinning icon is shown forever:
      7. Follow the same steps, but logged in to Crucible with an administrator, and see that the "Create Review" dialog will work as usual.

      Expected Results

      Regular users should be able to create create Jira issues from comments on Crucible review.

      Actual Results

      The "Create Issue" dialog shows up but a spinning icon is shown forever.

      When debug logging is enabled in Crucible side we can see the request from Crucible side resulted in a 404 response code when logged in as the regular Crucible user:

      2022-05-25 10:59:26,451 DEBUG [qtp1443055846-248 ] fisheye ProfilingServletFilter-logRequest - start request POST /json/cru/CR-2/reviewUpdatedAjax?backingOff=false&reviewStateName=Review&timeSpent=3479&reviewRenderTime=1653486613662&checkOwnActions=false sessionid=node04evl7k4hqhz614unvg2brrpfo5
      2022-05-25 10:59:26,453 DEBUG [qtp1443055846-248 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:26,455 DEBUG [qtp1443055846-248 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:26,461 DEBUG [qtp1443055846-248 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fkraemer' in directory 1 'Internal Directory'
      2022-05-25 10:59:26,472 DEBUG [qtp1443055846-248 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru2' in directory 1 'Internal Directory'
      2022-05-25 10:59:26,474 DEBUG [qtp1443055846-248 ] fisheye ProfilingServletFilter-logRequest - end request in 22ms POST /json/cru/CR-2/reviewUpdatedAjax?backingOff=false&reviewStateName=Review&timeSpent=3479&reviewRenderTime=1653486613662&checkOwnActions=false sessionid=node04evl7k4hqhz614unvg2brrpfo5 200 mem=2.075MB
      2022-05-25 10:59:26,476 DEBUG [qtp1443055846-203 ] fisheye ProfilingServletFilter-logRequest - start request GET /rest/branchreview/latest/trackedbranch/CR-2?_=1653486613840 sessionid=node04evl7k4hqhz614unvg2brrpfo5
      2022-05-25 10:59:26,495 DEBUG [qtp1443055846-203 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:26,497 DEBUG [qtp1443055846-203 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:26,501 DEBUG [qtp1443055846-203 ] fisheye ProfilingServletFilter-logRequest - end request in 25ms GET /rest/branchreview/latest/trackedbranch/CR-2?_=1653486613840 sessionid=node04evl7k4hqhz614unvg2brrpfo5 200 mem=0.801MB
      2022-05-25 10:59:26,703 DEBUG [Resource Monitor ] fisheye SystemResourceMonitor$MonitoringTask-run - tc=170, ofd=656, mfd=10240, fm=3313929240, tm=4156030976
      2022-05-25 10:59:28,845 DEBUG [notificationManager1 ] fisheye DefaultNotificationSender-lambda$sendNotifications$0 - Processing notifications
      2022-05-25 10:59:33,076 DEBUG [qtp1443055846-248 ] fisheye ProfilingServletFilter-logRequest - start request GET /rest/jira-ril/1.0/jira-rest/applinks?reviewKey=CR-2&_=1653486613841 sessionid=node04evl7k4hqhz614unvg2brrpfo5
      2022-05-25 10:59:33,077 DEBUG [qtp1443055846-22 ] fisheye ProfilingServletFilter-logRequest - start request GET /currentstatic/2static/images/blank.gif sessionid=node04evl7k4hqhz614unvg2brrpfo5
      2022-05-25 10:59:33,095 DEBUG [qtp1443055846-22 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:33,095 DEBUG [qtp1443055846-248 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:33,096 DEBUG [qtp1443055846-22 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:33,097 DEBUG [qtp1443055846-248 ] com.atlassian.crowd.manager.application.ApplicationServiceGeneric ApplicationServiceGeneric-findUserByName - Located user 'fecru1' in directory 1 'Internal Directory'
      2022-05-25 10:59:33,098 DEBUG [qtp1443055846-22 ] fisheye ProfilingServletFilter-logRequest - end request in 20ms GET /currentstatic/2static/images/blank.gif sessionid=node04evl7k4hqhz614unvg2brrpfo5 302 mem=0.604MB
      2022-05-25 10:59:33,098 DEBUG [qtp1443055846-248 ] fisheye ProfilingServletFilter-logRequest - end request in 23ms GET /rest/jira-ril/1.0/jira-rest/applinks?reviewKey=CR-2&_=1653486613841 sessionid=node04evl7k4hqhz614unvg2brrpfo5 404 mem=0.697MB
      

      Workaround

      The workaround would be to grant regular Crucible users the admin permission, however this should obviously not be done.

        1. image-2022-05-25-11-08-42-435.png
          60 kB
          Felipe Kraemer
        2. image-2022-05-25-11-12-24-678.png
          35 kB
          Felipe Kraemer

            Assignee:
            Unassigned
            Reporter:
            Felipe Kraemer
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: