Design proposal:

Mock ups from Bekah, UXD, that show a full create notifications flow, starting with the integrations wizard as a base.

• Overview link
• "Add integration" wizard
• "Create new group" wizard
• Miro (flow chart)

Background/context:

Currently if you navigate to settings -> notifications -> bundle of choice (e.g., openshift, rhel, console, etc) > create group, you will see this wizard (image attached to ticket - for some reason won't show up in the description directly).

Rather than driving users out of this wizard and sending them to settings -> integrations to set up a new integration, we should allow users to create a new integration in the same wizard.

Example mock from glepage@redhat.com :

Ideally, we would have the same wizard appearing for behavior group set up and integration set up.

CC: maryshak1996 – let me know what you think about Gwenneg's mock 

As part of this redesign of the behavior group wizard, simplify the language used as well (from dayle.parker ):

• The title or introductory text could be something like “Configure notifications by group”, and “Create a group to notify when an event occurs.”
  ‘Actions’ is about where to send the notification, so maybe it could be called ‘Notification method’ or channel. 
  For the Associate event types screen, the description could be something like  “Select the events to send a notification for/notify about”

Regarding updating the integrations wizard (from rhn-support-robwilli):

When setting up an integration, this can be a bit of a daunting task for someone not too familiar with this process. Today we offer various options (EDA, Google Chat, Splunk, ServiceNow etc) in which the "Add Integration" wizard changes the value of what is being added but provides minimal context behind those fields and nowhere to go for further information. If I as a user, become confused with what is being asked, I am most likely going to abandon the process altogether.

The ask here is to evaluate the current "Add Integration" process to provide additional details to the user to help guide them toward a successful setup for each of these types.

An example is: When I select ServiceNow, don't just change the fields on me, but also offer a link to guidance (of hover over help bubbles) that provides more details or points to a resource that tells me a bit more about this integration and what I may need to get going.

• Where would I find the endpoint URL?
• Why do I care about Enable SSL verification being checked or not?
• Where do I go for this secret token? 
• What are extras?

Providing this level of detail or supporting artifacts that are easy to find while in the setup process aims to lower the barrier to a successful setup.