Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,773
Community Members
 
Community Events
176
Community Groups

Tables in new Jira View Editor

Wiki markup supports creating tables using pipe characters. We use these extensively in our issue descriptions, and they render correctly in the new issue view.

However, if we edit the description the new (markdown) editor fails to load giving "This text has unsupported formatting" and we're left editing raw source.

Untitled 8.png

Worse, there seems to be no way to create a table in the new editor.

I searched for any info on this missing functionality and whether there are plans to restore it, but haven't found anything.

Any information/workarounds?

5 answers

Removing tables is a big downgrade in functionality. 

Kindly re-add support for markdown tables. I use them extensively.

This was a really useful feature of the old view. Very powerful in BDD where we start with examples. Also great for modelling data and report features.

1 vote

I have the same problem.

Don't know if it's a bug or if Atlassian remove the option for wiki markup tables in Jira.

but i have a workaround (that work for now).

When you are in your issue view, for exmaple:

xxxxxxxxx.atlassian.net/browse/NHT-1

 

Add "?oldIssueView=true" after your issue id, so your url will look like:

xxxxxxxxx.atlassian.net/browse/NHT-1?oldIssueView=true

 

Than you will have the option to add tables to your description field and it will be shown when you are back to the new look, it goes away if you will try to edit the field in the new look.

Thanks, yes I meant to mention that in my original question. My worry is that when the old editor and wiki markup are no longer available (which Atlassian makes clear is going to happen) we'll be stuck.

This is insane to be removed. We have tables with partly prefilled cells where we just fill in the response later in other cells.

This cant be used anymore and instead of a 2 sec copy and paste operation  the new mode will take up minutes per Ticket. Thats money going down the drain in work time. Not even talking about the pain of doing it the new way.

 

Also - people are now destroying my tables by editing them in the new editor?

 

How did this manage to slip through the quality control team?   Did this actually go through quality control?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events