`rasa visualize` does not show entities and slots relevant for the stories

h3. What problem are you trying to solve?

For our dialog designers to have a visual tool to look at and debug complex stories, they need to see where stories are identical and where they are different. As stories may differ by intents with entities and also by slots being extracted or provided by custom actions it is very important for us to show also entities and SlotSet events in the visualization.

h3. What’s your suggested solution?

Intents: instead of showing some sample user utterance from the training data, show the intent name together with entities, like user_intent(entity1, entity2)

SlotSet events should be shown comparably to actions, for the simple reason that the current solution does only support one intent in a row.

Have a look into #10932 for a working example (Python 3.8 only so far).

h3. Examples (if relevant)

stories:
 story: story1
 steps: 

    - intent: some_intent
      entities:
        -  supper
     - action: utter_supper

 story: story2
 steps: 

  - intent: some_intent
    entities:
     - lunch
  - action: utter_lunch

h3. Is anything blocking this from being implemented? (if relevant)

NO. Working example provided. Only little changes required.

h3. Definition of Done

Entities are shown together with intents, slot set events are shown in the visualization to explain connections.

[sync-by-unito[bot]]

➤ Maxime Verger commented:

💡 Heads up! We’re moving issues to Jira: https://rasa-open-source.atlassian.net/browse/OSS.

From now on, this Jira board is the place where you can browse (without an account) and create issues (you’ll need a free Jira account for that). This GitHub issue has already been migrated to Jira and will be closed on January 9th, 2023. Do not forget to subscribe to the corresponding Jira issue!

➡️ More information in the forum: https://forum.rasa.com/t/migration-of-rasa-oss-issues-to-jira/56569.

[rasabot-exalate]

Alan Nichol commented: Discussed this with Raoul today. We suggested separating out the bugfix from the new functionality (rendering slots and entities and branching on them). His point was that this feature can’t be used by them unless we support that new functionality, because the visualisation doesn’t reflect the lion’s share of their dialogue flows if it only branches on intents.

So I guess the meaningful unit of work to prioritise against other issues is “making the visualiser usable for Telekom”.