Project name should be a field so that the way it displays isn't dependent on location
I've been working with Wrike for 4 years, 1 year as an administrator, and still have yet to figure out a good way to structure projects because of how the project name displays. I've been trying to move my team to a kanban structure but it's very frustrating that the project name only shows the immediate next location not the actual project name. For example, say my team adds an email to a campaign and calls it "Product Promo Email" and adds it to the Marketing phase (folder) of the project (Campaign A). When I check the board, my to-do, reports, etc. I'll just see a list of emails with no idea what project they're for because that all just say "Product Promo Email" and "Marketing" or whatever that folder is called.
I've searched high and low but the only suggestion I've seen is to add prefixes to everything. I'd rather file my nails on a chalkboard than look at 500 tasks with prefixes that I would have to come up with when opening a project and track. Suffixes would be better visually but they can only be added via an automation that would be (yet another) workaround that eats into our monthly automation limits. Seems silly but if I want statuses to change to Ready when predecessors are completed and discern projects that's a minimum of 2 actions for every single item that's created. If I have 250 tasks then I'm eating up 1/4 of my monthly action allowance just creating tasks! This issue has been the bane of my existence as I'm trying to establish our PM processes so any suggestions are def welcome as well!
Hi Travis Balthes, thank you for your detailed post! In the Table view, you can enable the "Location" field to display all the projects/folders/Spaces where the tasks have been added to:
In case you'd like to use a more Kaban-style layout, the same option is available in New Dashboards:
I hope this information helps!
While this is helpful, I've run into the same problem. The 'Location' only shows 1 level up. We have the following structure:
- parentproject
- milestone
- subproject
- subtask
- subtask
- milestone
- subproject
- subtask
- subtask
- milestone
- subproject
- subtask
- subtask
The 'milestone' will show the 'parentproject' as the location.
The 'subproject' and 'subtask' item types under the 'milestone' show the 'milestone' as the location, not the 'parentproject'. This is troublesome when the 'milestones' names are based on stages and not updated per project.
For example:
In a dashboard, I'll have a list of 5 projects, all 'subprojects' of 'milestones'.
Milestone project name = project planning
The 'subproject' project names and locations would be the following:
project name location
- setup ecommerce platform project planning
- setup ecommerce platform project planning
- setup ecommerce platform project planning
- setup ecommerce platform project planning
- setup ecommerce platform project planning
I'll have to hover over 'project planning' in the dashboard to see which project it actually belongs to.