UI change - Project tabs/buttons in tasks pushed down


#230

I have been following this thread since the change. The only part of the change which we have a problem with is the moving of the “Project” area on the task view. This became a larger issue during training this past week. I was training new users on how to use multi home and the training videos are out of date.

Since it appears these changes won’t be converted back, is Asana going to update all the tutorials to handle the new format?


#231

“The thing I have noticed is when the anecdotes and the data disagree, the anecdotes are usually right. There’s something wrong with the way you are measuring it.”
Bezos


#232

Man, I really wish this would get addressed. I was in meeting with our CEO on Friday. He was in a task we were all reading through the description on screen and because the description field was so long it was hard to find what project the task was assigned to. 2 people took the mouse to scroll and try to find the projects/tags area. Each scrolled through it twice. It’s so hidden. Really should be at the top as users utilize the description field more and more as a notes area. We loose context of which project this is assigned to.

223 comments and growing.

Maybe we’ll get some Asana attention on this soon?


#233

If you guys are such power users, then just use the shortcuts? No need for UI.


#234

Yes the Tab-P shortcut is a good way to quickly get to the Projects section of a Task. But it still doesn’t solve the fundament problem that a long Task description separates a Task’s name, assignee, due date, etc, from the Projects the Task belongs too.

The primary request here, is to keep all the Task “metadata” together to be viewable at once.

If you were to design a program that list the files in a file system, you wouldn’t list the file name, owner, dates, then show the file contents, and then list file type after the contents.


#235

I can’t agree enough with that last sentence, Vince.

Whenever I’m training a new employee at our company on Asana, and they haven’t yet added the CSS that my colleagues wrote to fix the project-below-description issue, I literally can’t look at their Asana to help them out, because it’s so frustrating.

For those of you newer on this thread who haven’t read the backlog, there are a few different CSS fixes posted earlier here that will help you out. I still think Asana should fix it though, and listen to its userbase.

Our company is also considering moving away from Asana. It wouldn’t be my preference, since I still like Asana (given I am using a CSS fix for this issue), but I can see why they are considering it.


#236

It’s about much more than editing it…

The project a task is part of is essential metadata and should be visible in the same area as all the other metadata.

Using tab-p just to find the project is a ridiculous workflow. It also necessitates clicking out in order to see the category within a project that a task is in. Due to the already numerous pitfalls of using Asana, we’ve taken to using categories within a project as workflow states. With those, using the tab-p shortcut results in the following steps:

  1. Keyboard shortcut tab-p
  2. click out of projects list
  3. Look at project
  4. if adjusting the step, click on workflow state to adjust.

Alternately, you can scroll down below the description. I just worked on a task with over a dozen comments and a description containing the entirety of an email chain involving over 40 messages, so that’s not a great workflow either.

With the previous workflow:

  1. Look at project
  2. if adjusting the step, click on workflow state to adjust.

There’s the added problem that all of us “power users” are not the only ones using these systems. Sometimes we’re managing dozens of other people who are completely clueless about using computer systems in general and Asana specifically. Expecting everyone to just know these shortcuts is misguided. Promoting it as the primary way to access this feature (as Asana’s forum team is doing) is idiotic. It’s bad design, and bad customer service.


#237

Well said! I 100% agreed.

I spend a lot of time cleaning up task descriptions specifically to avoid the issue you’ve stated below – time I definitely don’t have to spend on things like this.


#238

Bummer that this still hasn’t been addressed by Asana…


#239

I sincerely doubt it will. They’ve chosen their path, and chosen to ignore any feedback on this issue. This thread might as well be closed for all the good it’s done.


#240

Wish this issue were already resolved :frowning:


#241

Try hitting “tab” after Tab+P, then you’ll be able to add it to an additional project!


#242

Thanks @Jordan_Katz. I tried it out and that worked. I appreciate your help.


#243

Just came by again to say my team is still not used to and not liking hunting down project names and having “Tags” hidden in the more menu instead of directly accessible by click (I’ve tried to get used to keyboard shortcuts, but that slows me down for different reasons - can’t tell you how many times I’ve opened a new tab in Chrome - tab+ as shortcut so unnatural compared to ctrl+)