Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-1949

[OCM UI] Lockbox: Access requests details show wrong/missing justification

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Core Sprint 255

      Description of problem:

      Opening the access request dialog, of an access request still to approve, from access requests tab of cluster details page, the justification created by the access request author is not reported. If the justification is denied with a justification, then if the user try too see the details dialog a justification field is shown, but the content is the justification text from the author of the access request and not as expected the justification text from the user denying the request.

      How reproducible:

      Always

      Steps to Reproduce:

      1. Open OCM UI staging.
      2. Go to cluster list.
      3. Click on one of the pending access requests shown on top of the page.
      4. In access request tab of the opened cluster details page click on "Open" button.
      5. Observe the access requests details dialog
      6. Deny the request writing a justification
      7. Reopen the access request details dialog
      8. Observe the access requests details dialog

      Actual results:

      At step 5, no justification is shown.

      At step 8, the justification shown is the one provided by the access request author.

      Expected results:

       At step 5, he justification provided by the access request author should be shown.

      At step 8, the justification provided by the user at step 6 should be shown.

            emingora Enrique Mingorance Cno
            rhn-support-vgrazian Vitor Graziano (Inactive)
            Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: