Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-5127

[ODC] Dev sandbox requires it's own area in documentation

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Undefined
    • None
    • OpenShift 4.12 Async
    • Developer Console
    • None
    • ---
    • ---

    Description

      Description of problem:

      Dev sandbox requires it's own area in documentation

      Version-Release number of selected component (if applicable):

      4.12.0

      How reproducible:

      Always

      Steps to Reproduce:

      1. Going via ? mark in Dev Sandbox UI and then clicking on Documentation - lands me to: https://docs.openshift.com/dedicated/welcome/index.html
and doing there search by "Dev sandbox" or "Developer sandbox" leads to "No results".

      Actual results:

      No presence of Dev sandbox related documentation

      Expected results:

      Have some presence of Dev sandbox documentation with some RBAC/etc. limitations/constraints listed

      Additional info:

       

      Attachments

        Issue Links

          is triggered by

          Feature Request - Feature requests from customers and/or users RFE-4041 Cannot make new Devfile as an option in Catalog

          • Undefined - Priority not specified.
          • Rejected

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-11001 Cannot retrieve image info from Dev sandbox internal registry

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-11256 Topology UI doesn't recognize Serverless Rust function for proper UI icon

          • 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

          Activity

            People

              rhn-engineering-nchaudha Nidhi Chaudhary
              andrejusc@yahoo.com Andrejus Chaliapinas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: