Rovo conversation starter UI bug?

[Nick Boxall]

In Rovo Chat, I’m seeing what looks like a UI bug with conversation starters for a custom agent.

I have configured only one conversation starter for the agent. However, when I open the agent in Chat, I see three conversation starter chips:

• The first shows my configured text

• The second and third appear as blank tiles with only the “launch” icon and no label

I’ve verified that the other starter fields are empty (no text or whitespace) in the agent configuration, but the empty chips still render. I would expect:

• Only the configured starters to be shown, and

• No visual placeholders / empty chips for unused starters.

Is this expected behavior, or a bug in the conversation starters UI? If it’s a bug, is there any known fix or workaround besides filling all three with dummy text?

[Barbara Szczesniak]

@Nick Boxall Welcome to the community.

This is not explicitly stated anywhere, but seems to be implied, I guess. On this page, https://support.atlassian.com/rovo/docs/conversation-starters/ , it says:

Although not required, we strongly recommend you create conversation starters for your agent. They provide people with the kinds of questions or instructions your agent is best at working with.

This looks like you don't need any, but then it goes on to say:

If you chose to create your agent using chat (instead of skipping to manual setup), we’ll generate conversation starters for you, but you’ll be able to edit them before finalizing your agent.

If you leave the field blank, your agent will use generic conversation starters.

This implies that there will be 3, no matter what. Not sure if you can have more than 3.

[Tomislav Tobijas]

Hi @Nick Boxall ,

So, I was building an agent to simulate this and I've asked my wizard/agent to leave only 1 conversation starter and leave the other two empty, and this is what I got as a response:

Just to confirm, the agent must always have exactly three conversation starters. It’s not possible to leave the other two empty or have fewer than three. If you’d like, we can keep your preferred starter and add two very simple, generic options, or you can suggest alternatives.

There doesn't seem to be an open feature request or bug for this on JAC.

This feels like it should at least be documented, and the feature request for adjusting the number of conversation starters could be created.
My suggestion would be to reach out to Atlassian Support, discuss this with them, and have them create a new suggestion so you can drop a vote.

Cheers,
Tobi