Project and folder structure display

I'm really having trouble telling where I am at times.  What task belongs to what project, what project belongs to what client, and even what team folder belongs to what project.  To that end, I created client folders under our projects, so only things we want the clients to see show up in their folders.  But on the client side, if they end up with multiple folders, it doesn't indicate where they come from.

So I'm thinking at the top of the page where it displays where you are, it could also show (even if it's smaller below the main title) the tree and project.  Something like:

Folder/Project name

[project name] next folder up, next folder up, next folder up, etc...


Design Tasks (larger, like it is now)

[Wage Recovery 2018] Office of Consumer Affairs < Consumer & Veterans Services  (smaller)


or you could do something that expands even vertically:
Design Tasks (this is the folder we are clicked on)

(expand folders/structure)

[Wage Recovery 2018]

Office of Consumer Affairs

Consumer & Veterans Services

2018 (top level folder)


So when I share a folder with someone, like the Design Tasks folder, but they don't have access to any other folders.  when they see it in their panel, it will only say "Design Tasks," but when they click on it... above the LIST panel it will show the folder name "Design Tasks" and smaller below it, it will show the path and highlight in some way the project it comes from.

But this idea of disconnecting the project from tasks seems to happen in a few places within Wrike.  And it makes it tough when you try and keep folder structure consistent, because you end up having a lot of folders with the same name, but when you can't see those folders in context to the project, it's tough to know where they come from.  And I really don't want to have to add the department to every folder name.  That seems like a waste.

6
10件のコメント
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Hi Francesco, thanks for this informative post. 

I think for this, the use of using tags on tasks with the appropriate client folder, source Project etc. will help you locate where the task is coming from. You can then simply hover over the tags to see the full 'breadcrumb' source where the task is in terms of the Folder tree.

Take a look at the above article on using tags to add tasks to Folders and let me know if this will help.

In terms of seeing more detail about where the task is created check out the below GIF where I hover over the tag and can see a more detail overview of where the task is created.

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

 I agree with the issue Francesco has raised -- we are having the same problem.  The solution you suggest doesn't work for me though, for two reasons.  First, it's more time managing tasks (applying tags) and second, it's a lot more wasted time "hovering" over a task to see what we need to see as at a glance.

The folder/project structure is the only real solution I've seen for organizing data across multiple clients.  Custom fields are too time consuming, and for other reasons, are not well suited for organization across folders and projects. If you are working with any template-like projects (eg. delivering the same project to different clients), searching and collective views (eg. My Work, inbox) become quickly confusing.  

Adding task prefixes is a potential solution, but ultimately adds to clutter.  Happy to provide further feedback, but I think this is a significant issue.  

5
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Thanks for adding your feedback Liz. Like all requests posted here, it will be brought to the attention of the Product Team. In the meantime, other members (like yourself 🙂) can vote and add their use-case and input for our team to review.

This is not something on the planned Product Roadmap right now, if and when there's a change to this I'll be sure to update this thread.

Thanks for posting and welcome to the Community 🙌

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Wrikers

I share the requirement of being able to see (without the use of tags) the Project name in the list of Tasks under the MyWork tab/menu.

Sure tags would work but why should we need to create additional steps when tasks a supposed to be bound to a project ?

Has this request been queued for dev/release ?

Thanks

Danny

4
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Please add me to the request. Being able to see the project where the task is coming from is imperative to keep track of things. Most projects will have sub folders that are not intended to be shared with everyone involved and sharing a sub folder with someone without access to the main folder is chaotic. Teamwork Projects has this feature where one can share or lock a file inside the main file and it works pretty well, so that tells me it can be done elsewhere too. Right Wrike? :) 

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Please add me as well. If you can see what folder a task is in then you should be able to see the root project its coming from or else you are guessing if you have templates you use over and over for folders.

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hey @Michael, thanks for bumping this post 🙂 I wonder if tags that Stephen mentioned above can help? You can use Folders and Projects as tags by adding a Task, Folder, or Project to another Folder or Project. Please let me know what you think!

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

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Lisa this doesn't help because when you are looking at tasks in My Work or a dashboard you can't tell what project they are coming for unless you name every single folder in that project. One of the biggest selling points for Wrike for most people I believe is the templates and being able to copy how you do a project over and over. now you have to go in and rename all the folders in your template each time instead of having the task just show PROJECT/FOLDER opposed to it just showing FOLDER right now. Its a very simple solution.

2
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Bump. It looks like I can hover over the tag to see a path for any given object, but that isn't possible unless you have permission to the parent object that wasn't explicitly shared to you? What are the conditions where a user cant see a tag and thus be able to see the path of something they were assigned or have been @ mentioned on?

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Patrick MacArthur,

Thank you for your question!

In order to maintain the security of your Wrike data, users can only see the items in Wrike that have been shared with them. So if you share a task with someone, but the parent folder, project, or space isn't shared with them, then they won't be able to see the full pathway where the task exists.

Here is an example of what the user will see when they hover their mouse over the tag of a task when the space, folder, and project (the full pathway) have all been shared with them:

If the space isn't shared with them, but the folder and project are, this is what they will see:

If only the project is shared with them:

And if only the task is shared with them, then they won't see any tag at all:

For the most part, sharing is inherited from the top down. This means that if you share a space with a user, then they can see all folders, projects, and tasks within that space. If you share just a folder/project, then they can see everything within that folder/project. And if you share only a task, then users can only see the task and any subtasks it may have.

As a side note, there can be exceptions to inherited sharing rules for users with the Enterprise subscription, as they have the option to set selective sharing up on the folder/project level.

One last thing to mention, for users that have access to the full pathway of a task and who are using the New Experience feature, it's possible to see the full pathway of the task with just a glance at the top of your workspace:

Please let us know if you have any questions.

Have a productive day! 😄

Aaron K. Community Team at Wrike Wrike Product Manager Learn about Wrike’s killer features and best practices with our Online Training Webinars

Aaron K. Wrike Team member Learn about Wrike’s killer features and best practices with our Online Training Webinars

0
コメントアクション Permalink

Folllowing List for Post: Project and folder structure display
[this list is visible for admins and agents only]

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