Confiform to Jira JSON Description Field Table Loses format structure when editing in Jira

[Stefanie Hayden]

The question is: Is there another JSON where fields not mapped to custom fields in the Jira scheme submitted through the Confiform process are mapped into the Description field, then formatted into a Table, keep its structure and allow users to edit the data within the cells?

Scenario:

Currently, when a form is submitted using the standard JSON format of:

(this is a table example using || for column header separation, | for row name, field name separation and \n for carriage return)

||*INTAKE QUESTION*||*INTAKE RESPONSE*||\n|*Requestor Name*|[entry.RequestorName.escapeJSON]|\n|*Requestor Email*|[entry.RequestorEmail.escapeJSON]|\n|*Executive Sponsor*|[entry.ExecutiveSponsor.escapeJSON]|\n|*Business Owner*|[entry.BusinessOwner.escapeJSON]|

The table in Jira looks great but when a user edits the information in the table, the structure collapses. 

Additional Outcome: If the user has submitted a substantial amount of text for one of the fields which is allowed (400-500 words) the field distorts the 1st column and there is no way to adjust the table for that particular record.

Current Status: There has not been another way to transport the form information I have found.

[David Shahbazyan]

Hi, @Stefanie Hayden 

no, there isn’t another JSON format that will do this.

What you’re seeing is a Jira limitation, not ConfiForms. Tables created in the Description using wiki markup (||, |) render fine initially, but when a user edits the issue, Jira’s editor converts the content and breaks the table structure.

Also, column widths in Description aren’t fixed, so long text will always distort the layout.

Options:

Use custom fields (best for editable data)
Use ADF JSON for better table behavior (still not perfect)
Keep the table for display only and store data separately

If users need to edit the data reliably, Description tables aren’t the right approach.