That’s very true Tyler, you were able to move tasks between sections using the drop down which I actually use. But that functionality still exists. It wasn’t removed. So yes it was a bit more than just “pretty”.
Having said that, we’ve repeatedly ran into this wall of them not being able to iterate further with Section Headers because of the data models they used when creating them. From a programming/database standpoint this is fully understandable and expected. Which is why the update needed to happen.
Again, Tab+N or Shift+; are the same amount of keys pressed. One is done before you type/paste the other is done after you type/paste.
I get that some people created a list elsewhere and then pasted the whole thing in and it autocreated headers. This can easily be fixed through the import feature.
Again, my point is that it’s not harder to push two keys than it is another two keys. People just dont like change. Without change there can be no advancement. Rather than asking to revert back to a bad data model with no future lets try to give suggestions on how to make the new model work better:
- When hitting Tab+N create a new section directly below your current selection
- Allow for sections to be created at import. This could even be set up the old way and Asana detects any task with a : at the end and creates a NEW header data type instead of old task header.