Shared Tasks lack context

Among many other issues we're finding, we've discovered that the sharing of tasks is nearly useless without the context of the project, space, or task list/folder that it's within.

For example, our PM just shared a task with me and there was some limited conversation going on. I got an email that was subject "RE: Client Revisions" with literally no other information aside from the conversation. Half the time, similar convos could apply to a myriad of clients and/or projects here.

Although I can see the need for limiting permissions and access BEYOND that single task, not giving that person some idea of where they landed in wrike is absolutely mind-boggling. In that case, the parent project/folder/space should be labeled within the task as it normally is for users with appropriate permissions, just not clickable.

Attaching an image. What good is this without some context of where it is?

6
6 comments
Spot On Innovative Approach Stellar Advice
Avatar

I prefix my tasks within projects and therefore continue to have a reference.  See pic below.  This means for us that we know which project the task is from.  

 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thanks Glyn — our problem unfortunately is not solved just by naming conventions. We have so many clients and so many separate jobs under those clients, that a naming convention to encapsulate all of that without getting incredibly hard to decipher is impossible. And using our agency's job-number format (XXX-####) is great if you know what the job is, but that adds a level of duplicated manual editing that should really just fall under the organizational hierarchy.

The fact for us remains — and this goes way beyond just shared tasks as I've pointed out above — that Wrike is not using the inherent organization that they've pushed us to use (spaces, projects, folders) to properly label, sort and/or filter tasks and conversations without hyper-customized modules in dashboards or manually-entered information (like prefixes). It takes away the automation and usefulness of that top-down hierarchy — something that is seen in much cheaper and feature-limited systems like Asana and Basecamp.

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I'm seeing the same deficiency being noted in several other threads on this forum. Glyn's solution works, but isn't practical at scale. It should be something inherent in wrike's UX, and not something that anyone needs to fudge a workaround for. Unfortunately, it appears that problems need 60 upvotes to get flagged for their development team, and that seems to be a pretty high bar to achieve. 

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hey everyone! This is a very interesting discussion! I wonder - do you usually have empty task descriptions? Because this is a good place to add info and therefore have context. Please let me know whether this works for you! 

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Our task descriptions always have info, but as noted above, this is not a good place for that context. I've attached a mockup of what would work better within your to-do layout. It's clear that you have the capability to display the folder (or client) name, because that path is displayed in an overlay when you roll over another element. (In my mockup, that element is the one that has the highlighted background color). This is important information. An action (a hover) should not need to be performed in order to see it. It should be immediately viewable, across the board. This context is important, and missing from many places in your platform. It would improve our experience with wrike tremendously to implement something like this. The attached solution can be applied to 

  1. Email notifications
  2. Timesheets
  3. App notifications
  4. Every panel within a job / folder / space / task
  5. To-Do lists
  6. Inbox Messages

 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Ken Stanek, thanks a lot for getting back to me! Your feedback will be passed to the team 🙂

Lisa Community Team at Wrike Become a Wrike expert with Wrike Discover

0
Comment actions Permalink

Folllowing List for Post: Shared Tasks lack context
[this list is visible for admins and agents only]

Didn’t find what you were looking for? Write new post