Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-20715

Add validation for a project name in case of duplicates

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Optional
    • 4.3.1.Beta1
    • 4.3.0.CR1
    • openshift
    • None

    Description

      There could be a simple validation of a project name for duplicates. It should not be necessary to hit Finish button in Create OpenShift Project dialog to find out that project already exists based on response from server. Simple validation based on existence of a tree item of project or some similar mechanism would be helpful.

      Attachments

        Issue Links

          is cloned by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-21010 Add validation for a project name in case of duplicates

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Closed
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-21184 Deploy docker: "Resource Name" should not error (but "*" required) if empty

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-21394 Deploy docker: "Resource Name" should not error (but "*" required) if empty

          • 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

              fbricon@redhat.com Fred Bricon
              mlabuda_jira Marián Labuda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: