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

Application Wizard: Resource label key has wrong label

    XMLWordPrintable

Details

    • devex #147 April 2018
    • 1
    • Hide

      ASSERT: Have an OpenShift 3 connection with a project.
      EXEC: Open New OpenShift Application wizard.
      EXEC: Proceed to Resource labels wizard page.
      EXEC: Select an existing label and edit it, or try to add a new label.
      ASSERT: Resource Label dialog is opened.

      RESULT: There are 2 text widgets labeled with label "Label:" and "Value:"
      EXPECTED RESULT: There should be 2 text widgets labeled with "Key:" and "Value:"

      Show
      ASSERT: Have an OpenShift 3 connection with a project. EXEC: Open New OpenShift Application wizard. EXEC: Proceed to Resource labels wizard page. EXEC: Select an existing label and edit it, or try to add a new label. ASSERT: Resource Label dialog is opened. RESULT: There are 2 text widgets labeled with label "Label:" and "Value:" EXPECTED RESULT: There should be 2 text widgets labeled with "Key:" and "Value:"

    Description

      In New Application wizard on the page with labels, if I select to create/edit an existing label there is opened a dialog with label details. Label consists of key:value pair (it comes from kubernetes concept), but in this labels of text widgets are "Label:" and "Value:". I think we should have it labeled as "Key:" and "Value:" instead.

      Attachments

        1. resource-labels.png
          resource-labels.png
          33 kB
        2. screenshot-1.png
          screenshot-1.png
          25 kB
        3. screenshot-2.png
          screenshot-2.png
          119 kB

        Activity

          People

            adietish@redhat.com André Dietisheim
            mlabuda_jira Marián Labuda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: