Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-11593

Choosing channel name in Slack allows inserting unexisting channel name

    XMLWordPrintable

Details

    • Fuse 7.5 Sprint 52 - Bug fix

    Description

      The channel dropdown in Slack connection is as input type. After click on them, the datalist is shown with the available channel. Hence, the user is able to fill in the name of the channel which doesn't exist (or just make a TYPO error). The Slack connection wizard doesn't verify whether the channel exists or not. In that case, when the slack connection is:

      • as a start step (Reading from channel operation), the integration is never triggered. Which make sense when the channel doesn't exist.
      • as a middle or final step (Send a message to a channel), no errors are shown. It can be confusing for a user who e.g. makes a TYPO in the channel name because the integration is running without any errors but they doesn't see any messages in the channel.

      In my POV, the channel element in the Slack connection (Send a message and read a message action) should be only dropdown with all available channel without possibility to add something else. Or is any use case when the user wants to add the name of the channel which doesn't exist?

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-11787 Reconfiguration of SQL query step changes text to dropdown

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-11282 Google calendars select calendar dropdown changed to text input

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Done

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-11719 Choosing Resource Collection in OData allows inserting unexisting resource collection name

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

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-11758 Restore behavior of dynamic action metadata lookup form field rendering

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

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-11843 Text field instead of dropdown in the Salesforce connection

          • 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.
          • Done

          Activity

            People

              Unassigned Unassigned
              mkralik@redhat.com Matej Kralik
              Matej Kralik Matej Kralik
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: