Custom table not formatting in Description field if work item is created via global 'Create'

[Adam]

I have a table configured in the description field of my custom Content Update work type in Jira cloud. The table is part of the default template of this field so that it is shown on creation of a new work item with the 'Content Update' type.

The issue I am experiencing is that if a work item with this type is created via the global 'Create' function and not as a child to an existing Epic, the table does not format as expected.

Please see the examples below.

VIA EPIC

VIA GLOBAL CREATE

Any support would be greatly appreciated.

[Arkadiusz Wroblewski · Accepted solution]

Hello @Adam 

That´s team managed or company managed space ?

Best,

Arkadiusz 🤠

[Adam]

Team managed

[Arkadiusz Wroblewski]

@Adam 

That was Created with this Guide ? 

How to Add Tables in Jira Default Description (Cloud) | Jira and Jira Service Management | Atlassian Support

Issue is probably caused by global Create using a different editor path.

Jira Cloud has had limitations around tables in default Description templates, especially where old wiki-style table markup is involved. Atlassian’s documented workaround is usually not to rely on the Description default rendering during create, but to apply the table after creation.

[JRACLOUD-78176] Unable to add Tables in the Default description field using the new editor - Create and track feature requests for Atlassian products.

You can use a Jira Automation rule to insert the table template into the Description immediately after creation. Alternatively, you can use a temporary custom paragraph field on the Create screen to hold the default template, then automate copying it to the system Description field post-creation.

Best,

Arkadiusz 🤠

[Tomislav Tobijas]

Hey @Adam ,

As you mentioned, you're using team-managed space, san you share how you've configured this default table to actually show up? (like, screenshots and/or examples would be helpful)

I do have something similar built in my personal space and I'm using default value feature for it, and it shows how you'd expect, either in the create modal window and after creation. Although I'm using company-managed space here. 👀

UI should use Atlassian Document Format (ADF), but it may be that, in some cases it uses legacy Wiki Markup (I've seen it once or twice).

Cheers,
Tobi

[Arkadiusz Wroblewski]

@Tomislav Tobijas  Theoretically agree 👍 but "should use" is always something what I like to See 😅😊🤣

I've seen plenty of different behaviors, sometimes inconsistency between Editor in Pre and post action leading to some things like user asking here 🤔.

In general, I've noticed after the UI changes in the last few months, the Editor handles post-actions much better than during creation, but that doesn't really surprise me. 👍🤔