Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-8460

When user tries to edit a shared project UI gets stuck in loading without reporting errors

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • RHODS_1.28.0_GA
    • RHODS_1.27.0_GA
    • UI
    • False
    • None
    • False
    • Testable
    • No
    • 1.28.0
    • No
    • Hide
      == When editing the details of a shared project, the user interface remained in a loading state without reporting an error
      When a user with permission to edit a project attempted to edit its details, the user interface remained in a loading state and did not display an appropriate error message. Users with permission to edit projects cannot edit any fields in the project, such as its description. Those users can edit only components belonging to a project, such as its workbenches, data connections, and storage.

      The user interface now displays an appropriate error message and does not try to update the project description.
      Show
      == When editing the details of a shared project, the user interface remained in a loading state without reporting an error When a user with permission to edit a project attempted to edit its details, the user interface remained in a loading state and did not display an appropriate error message. Users with permission to edit projects cannot edit any fields in the project, such as its description. Those users can edit only components belonging to a project, such as its workbenches, data connections, and storage. The user interface now displays an appropriate error message and does not try to update the project description.
    • Bug Fix
    • Done
    • No
    • Yes
    • None
    • RHODS 1.28
    • High

    Description

      Description of problem:

      related to RHODS-8374 . If it's expected that a user B cannot edit the project details of a DS project shared by user A, this should be clear to the user B itself. While, user B can through UI trigger an edit of the DS project but UI keeps loading without returning any error message.

      GIF:

      After 7 minutes the GIF was captured, the UI was still in the same state.

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Create a Data Science Project myprojectA with user A
      2. grant "Edit" permissions on "myprojectA" to user B
      3. check user B can access the DS project "myprojectA"
      4. edit Description and/or name of "myprojectA" using user B

      Actual results:

      UI is stuck loading

      Expected results:

      either UI does not allow user to start editing the project or the UI reports an error when the "Update" button is clicked.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      RHODS v1.27.0

      Workaround:

      to close the update model: click "cancel" button or "X" icon 

      However the workaround wouldn't solve the UX issue

      Additional info:

      the same happens when the user tries to delete the project. However it is not clear if deletion is included in the requirements of "Edit" permission jdemoss@redhat.com 

      Attachments

        Issue Links

          is caused by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RHODS-7406 Enable project sharing

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. RHODS-8931 Emojis should not be allowed when creating or updating Data Science Projects in names or descriptions

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          mentioned on

          GitLab Merge request - Updated 2 upstream sources

          Activity

            People

              aballantyne Andrew Ballantyne
              rhn-support-bdattoma Berto D'Attoma
              Berto D'Attoma Berto D'Attoma
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: