Custom icons specified in manifest get narrowed in the listing

Hello everyone.

We’ve recently encountered a couple of issues while working with custom icons for our Rovo agent.

  1. After setting a custom icon by adding it to the manifest file, we noticed that the icon appears compressed (narrowed) in the listing after the agent is installed. It seems that in the page code, this custom icon is displayed using an <img> tag. In contrast, default icons for other Rovo agents are displayed via <svg>, which do not have this narrowing issue. This leads us to believe there might be a rendering issue with custom icons in Rovo. Our original icon is in png format. But we also witnessed the same behaviour for svg and jpg formats. Please see the attached screenshots.

  2. Additionally, we’ve faced another problem with the agent’s name and description. In the manifest file we specify a name for an agent. Example: we’ve created (via a dev console) and installed “Structure View Builder” agent. name in the manifest: “Structure View Builder”. After it is installed, it’s name is shown correctly. However it’s description in the listing also contains this name after “by”. So in general it reads as “Structure View Builder by Structure View Builder”. Looks a bit strange. We’re not sure why this is happening because we’ve just specified a name property in the manifest file. Please also see the screenshot. Note that in this case the icon looks normal because I’ve stretched the Rovo section so that the description fits into one line.

We’d appreciate any insights or advice on resolving these issues.

Thanks in advance for your help!

1 Like

More screenshots

Hi @VitaliiUshanov ,

For the problem about the icon not being sized correctly, this seems like a bug so could you raise a support case here please. The support team should be able to help you get to the bottom of the problem.

For the second problem, this is the same as that reported in The vendor name is not displayed on the agent when listing the app via Browse Agents. I raised this with the Rovo team and created ROVO-554 (internal to Atlassian), but the team have not provided an estimate of when this will be addressed. I’ll ask the team again.

Regards,
Dugald