Incorrect HTML structure in task description for lists

English Forum Tips and Tricks
1

Important note: To help us resolve your issue as quickly as possible, please ensure to fill out all the sections below. Do not share any private information such as email addresses or phone numbers - This is a public Forum!

Briefly describe (1-2 sentences) the bug you’re experiencing:
Unordered bullet lists in tasks are using the “ol” HTML-element instead of “ul”. Indentation is also not created using sub-lists but padding. This makes copying the lists to other programs a hassle since the indentation is not correct and the lists are always set as ordered lists even though they are unordered.

It would increase productivity a lot if the HTML-structure would be web standard.

Steps to reproduce:

  1. Create an unordered list in an Asana task description.
  2. Copy the description and paste it into another program (for instance Google Docs).
  3. See that the unordered list becomes an ordered list.

Browser version:
Chrome 123

What version of Asana are you using (Personal, Starter, Advanced, Enterprise, Enterprise+, Premium, Business or legacy Enterprise)?
Business

Upload screenshots below:

image
image1346×606 8.22 KB

image
image748×586 12.6 KB

When making the exact same thing in Google Docs I get this result:

image
image848×640 13.6 KB

3 Likes
2

Hi @Martin_Werner ,

I have been able to replicate this issue with both Google Docs and MS Word. I’m thinking this is less a bug than a feature request, but I’ll wait for the Asana team to weigh in on redirecting the post.

As far as I can tell, the issue is that Asana stores this info in their db correctly (verified by calling their API on a task with ul and ol elements in the description and returning the html_notes property, which correctly returns distinct ol and ul lists, including sub-lists), but they render all lists using ols, using data-list properties on the li’s themselves to present the right visuals.

3

Hi @Martin_Werner and @Stephen_Li, thanks for your comments. I’ve reached out to our Developers to confirm if this is expected and will get back to you once I have an update!

1 Like