Details

    • Type: Feature Request Feature Request
    • Status: Closed Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.0
    • Fix Version/s: EAP_EWP 5.1.2
    • Component/s: Embedded Jopr
    • Security Level: Public (Everyone can see)
    • Labels:
      None
    • Release Notes Docs Status:
      Not Required
    • Docs QE Status:
      ASSIGNED
    • Bugzilla Update:
      Perform
    • Similar Issues:
      Show 7 results 

      Description

      When testing if a connection for a datasource can be obtained through the Admin-console, the whole UI for that operation is confusing and misleading. User tends to interpret the results of the "Test Connection" under "Operation History" as the result if the connection has been successfully obtained or not, where in reality that section is just reporting that the operation "Test Connection" has been executed successfully, and nothing to do with the connection is obtained or not. The actual result for that is in the section below called "Selected Operation History Item".

      This is confusing to operational admins looking at this UI to test a connection. In fact, this would mislead them to look at the wrong section and proceed thinking the connection has been obtained when it's not, and could possibly cause serious production ramifications. The UI should be re-worked and be more intuitive and clear.

        Issue Links

          Activity

          Hide
          RH Bugzilla Integration
          added a comment -

          Charles Crouch <ccrouch@redhat.com> made a comment on bug 710230

          I think we should investigate whether a still better solution is possible for
          the Test Connection case. In that particular instance we should investigate
          simply making the operation return a failure status if the internal call to the
          AS to test the connection fails.

          Show
          RH Bugzilla Integration
          added a comment - Charles Crouch <ccrouch@redhat.com> made a comment on bug 710230 I think we should investigate whether a still better solution is possible for the Test Connection case. In that particular instance we should investigate simply making the operation return a failure status if the internal call to the AS to test the connection fails.
          Hide
          RH Bugzilla Integration
          added a comment -

          Larry O'Leary <loleary@redhat.com> made a private comment on bug 710230

          Show
          RH Bugzilla Integration
          added a comment - Larry O'Leary <loleary@redhat.com> made a private comment on bug 710230
          Hide
          Jan Martiska
          added a comment -

          This is fixed in EAP 5.1.2.

          Show
          Jan Martiska
          added a comment - This is fixed in EAP 5.1.2.
          Hide
          RH Bugzilla Integration
          added a comment -

          Jay Shaughnessy <jshaughn@redhat.com> changed the Status of bug 710230 from ASSIGNED to NEW

          Show
          RH Bugzilla Integration
          added a comment - Jay Shaughnessy <jshaughn@redhat.com> changed the Status of bug 710230 from ASSIGNED to NEW
          Hide
          RH Bugzilla Integration
          added a comment -

          Jay Shaughnessy <jshaughn@redhat.com> made a comment on bug 710230

          "Completed" may be the best thing to do here. Asking ccrouch for direction on this one.

          Show
          RH Bugzilla Integration
          added a comment - Jay Shaughnessy <jshaughn@redhat.com> made a comment on bug 710230 "Completed" may be the best thing to do here. Asking ccrouch for direction on this one.

            People

            • Assignee:
              Unassigned
              Reporter:
              David Chia
              Writer:
              Jared Morgan
            • Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: