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

CRW 3.0 Story #1 UG Starting a workspace

    XMLWordPrintable

Details

    Description

      • Starting a workspace using the dashboard. => Do we need to document this?
        • sample
        • git
      • Writing an URL to start a workspace

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3788 CRW 3.0 Story #1a UG Starting a workspace using a code sample from the dashboard

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3789 CRW 3.0 Story #1b UG Authoring an URL to start a workspace

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3790 CRW 3.0 Story #1c UG Starting a workspace using a public Git repository in read-only mode

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3791 Dev Spaces 3.x Story #1d UG Starting a workspace to contribute to a public Git repository

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3792 CRW 3.0 Story #1e UG Starting a workspace to contribute to a private Git repository

          • 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

          Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3793 Dev Spaces 3.x Story #1f UG Starting a workspace to contribute to a private Git repository behind a proxy

          • 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
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RHDEVDOCS-3521 CRW 3.0 Story #2 UG Contributing for the first time to a project

          • 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
          links to

          Web Link che blog DevWorkspaces articles publishing planning

          GitHub eclipse-che/che-dashboard#417: feat: allow to specify policy creation in short form syntax

          Activity

            People

              rhn-support-mleonov Max Leonov
              ffloreth@redhat.com Fabrice Flore-Thébault
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: