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

Application wizard: a user should not be able to create a label with the same name as a readonly label

    XMLWordPrintable

Details

    Description

      In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label). After the label is created it it not possible to edit/remove it.

      1. Create a new application from template
      2. Navigate to the 'label' page
      3. Add a label with the name 'template' which is a readonly label
      4. Note you are able to add a label that has a name that is readonly
      5. EXPECT: To not be able to add a 'readonly' label and are presented with a warning message.

      Attachments

        Issue Links

          is caused 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-20082 Application wizard: it's not userfriendly

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19952 v3 Application wizard: Template label decorators don't go away

          • 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-19975 v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling

          • 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

          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-21411 v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling

          • 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

          Activity

            People

              jcantril@redhat.com Jeffrey Cantrill
              mlabuda_jira Marián Labuda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: