Unsupported data inside long text fields

Symptoms

A Snapshot macro works as expected, but an error message like this appears in one of the rows:

The error message appears inside a field which is a long text field in Jira. The Description field is one example of such a field.

Why does this happen?

In the value that Snapshots has received for this issue and that field, there is a part that Jira Snapshots was not able to parse. It does not comply with some conventions and with how we expect the data to look like.
The error states the reality: we see there is information that we can’t display correctly. The error shows exactly in the location of the field where the unsupported data appeared. This location gives you a hint of what data in Jira triggers this error.

How to overcome this?

The immediate way to resolve it is to change the Jira data to be more normal. We give below the examples that we ran into when this happens and explain what to do.
If you did not find your exact situation here, would be great if you could drop us a line on support@radbee.com . Over time we are hoping to increase our support for these scenarios so that we never show this error.

Here are the known scenarios that trigger this error:

Tables that were created outside Jira, for example, with merged cells

Jira Snapshots can render tables that are created in Jira. But sometimes, we find tables that are not native to Jira and were created on other platforms. For example- you could create in Confluence a table with merged cells and copy/paste it to Jira. Natively in Jira- you cannot create tables with merged cells. When Jira sends us such tables over the API, it replaces its usual patterns with another way of rendering the table. Jira Snapshots does not support this way of rendering.

Example of a Jira field with one normal and one abnormal table:

How to solve this?

Recreate this table natively in Jira. Any format you can create in Jira will also be supported by Jira Snapshots.

This did not help?

Contact us on support@radbee.com