New feature - WBS

Hi,

I am missing the possibility to create, oversee and work with a WBS directly in wrike.

For me this is a very important feature to have when planning a project. I often start by making a wbs and then create my project, folders and tasks in wrike.

It would make a lot of sense if I would create my WBS directly in Wrike.

Thanks

//Oskar

Find more posts tagged with

On hold

Status: On hold

Comments

Margo Heston

I strongly agree, we've been interested in seeing/manipulating the folder and project relationships as a network for a while.

Francis JEANNIN

Agree also with this feature, some of my customer want this WBS

Leonardo Corredor

Hi, I would love having WBS directly in Wrike. Doing a WBS is an easy and more graphic way to start a project. Please add WBS to wrike

Joe Moran

This please!

Paul Steinfort

i agree, if Wrike had a WBS interface it would sell thousands if not millions more product

Marco Cavadini

Wrike is a great platform, but it's really missing a serious WBS tool or interface. A must have feature

Kristian Komjati

Would be a must have feature..!!

Brian Davis

I have requested this under Lead and Lag Times and it is also requested under Addind Dependencies. Can we combine these three into one request and get more votes?

[Status: Coming Soon...🕑] Leads and Lags with Dependencies
/hc/en-us/community/posts/115000170609--Status-Coming-Soon-Leads-and-Lags-with-Dependencies

[Status: Backburner ⌛️]Adding Dependencies to tasks with no Date field
/hc/en-us/community/posts/115003104589--Status-Backburner-Adding-Dependencies-to-tasks-with-no-Date-field

All three of these requests are showstoppers for migrating from MS Project. And, if Wrike could do this with the new blueprint feature, we would really be cooking with gas!!!

Brian Davis

If anyone is interested in resolving the "New feature - WBS" this issue as part of the new Lead and Lag time implementation, please comment on my post in Lead and Lag times:

/hc/en-us/community/posts/115000170609/comments/360003837513

I think your feedback on in-task GUI for dependencies should be implemented as part of the upgrades Wrike is doing with dependencies for lead and lag. The first step to WBS is to have a dependencies with no date become a reality.

Simona Rutulis

This a must have feature for sure! Wrike team, do you have any plans on adding WBS?

Carolin Mohr

Hello Wrike Team,

we need also a WBS tool! 👍

Romain THOMAS

Add this feature please

Elizaveta Bogdanova

Hello everyone, thanks for your support for this suggestion 👍 For now, this is not on our Product team's short-term roadmap, but if this suggestion gets more attention and upvotes, they might take a closer look. I wonder whether Table View and Gantt Chart functionalities can help you achieve what you are looking to do? It would also help a lot if you could explain the process of what you are looking to do with WBS in more detail 🙌 Thank you!

Carolin Mohr

Hello Lisa, thank you for your informations. Attached you will find a screen shot from a wbs tool. It would be great if you can develope something like this.☺️👍

Best regards

Bildergebnis fÃ¼r wbs

Romain THOMAS

Hello,

This feature is correctly well explained in your web site

https://www.wrike.com/project-management-guide/faq/what-is-work-breakdown-structure-in-project-management/

Before sequencing the tasks, it is very important to define them progressively from a large scope to shorter scope

A Mind mapping can be used to define the WBS

Thank you for moving this feature in an highter priority

Romain

Simona Rutulis

Lisa Bogdanova,

By looking at all the previous comments on this thread it's pretty obvious that there is a lot of interest in having WBS in Wrike! As for your comment "I wonder whether Table View and Gantt Chart functionalities can help you achieve what you are looking to do" - there are big differences between table view and Gantt chart, and a Work Breakdown Structure!

Elizaveta Bogdanova

Hey guys, thanks a lot for your examples, really appreciate them 🙂 What I meant was, the fundamental thing about WBS is the ability to break your work into smaller items, which can be achieved in Wrike by creating folders/subfolders, projects/subprojects, and tasks/subtasks. That is why I thought that the Table View or the Gantt Chart might be the places to plan and create work, Gantt Chart being more fit to see the full picture (timeline) of the future project.

It will be great to have more detailed examples with your use-cases to understand your need, and how say the Table View or the Gantt Chart might be insufficient for you. After that, when the suggestion hits 60 votes, the Product team will provide a Status for the suggestion - please learn about Product Feedback statuses here.

So for now, it's really important to get more votes here; I'll refer other Community members with similar suggestions here to +1 the post.

Thank you very much for your comments 👐

Joshua Lamorie

The table view seems pretty powerful, but it appears to have some bugs in the UI that doesn't let me do this smoothly.

I created a column named 'WBS' to have the WBS ID, as text (so I can do a.b.c) but it is smart and tries to turn the a.b into a number.

Joshua Lamorie

Using the earlier example

Joshua Lamorie

I'm liking this quite a bit, but there are some massive bugs that are making this really difficult to work with. I had hoped to have them show up in the example, but they only seem to be present in my more complicated (and more private) project work.

1) The WBS ID field I am adding manually, and it would be great if this could be auto-populated. Having these IDs allows us to have simple names for work packages without worrying about making them globally unique.

2) As I am adding subtasks, the UI seems to make the parent disappear after I have added, or display twice the same subtask. Every now and again I have to reload the entire page.

3) It's great to have custom fields and display them with variable lengths in the table view. However, when I look at fields in the task detail view, there doesn't appear to be a way to change the display width. They are all divided equally.

Improving the Table view would make it much easier to convince people to use this as a WBS replacement, but it's a real struggle at the moment.

Joshua Lamorie

Wow, a lot of other forum submissions about adding better WBS support to wrike:

If we combined all of these votes into one it would be something like 70.

What's the minimum needed to get it into the backlog?

Elizaveta Bogdanova

@Joshua Hey, welcome to Community, happy to see you here 🙂

Thank you for the screenshots and examples, they will help a lot when our Product team reviews this feature suggestion.

As for the other threads where WBS is discussed, we can't combine all those threads into one. I can close the other threads and post a link here instead, but I don't think that I should do that now because, although most of the threads touch the subject of WBS, they are not exactly duplicates.

Please +1 the original suggestion if you haven't already.

Thanks for commenting and happy posting 🙌

Wolfgang Konetschni

As our company is mostly dealing with classic project-management methods we see a strong need for the WBS as shown in this thread!

In Projectmanagement for Industrial system and solutionbusiness WBS is almost in each project requested by our customers

Joshua Lamorie

@Lisa, thanks for responding.

Replying to @Lisa

> As for the other threads where WBS is discussed, we can't combine all those threads into one.

Yeah, I understand, and I wasn't meaning to merge the items' contents at all, but just looking at the points/voting system that you use to determine community interest. How do you use these numbers?

Jessica Deike

Dear all,

as I'm only receiving irregular notifications from this thread (and this one seems to be the most suitable when it comes to a WBS-feature) I would suggest to activate your teams/users internally and ask them to vote for this feature.

Kindest,

Jessica

Elizaveta Bogdanova

@Joshua, thank you for getting back to me 🙂

We look at the number of votes regularly. We also report all the feedback to the Product team and when we get updates, we get back here to communicate them. You can learn more about what happens with Product feedback here.

When the idea reaches 60 votes, we add a Product Feedback status to the post.

Please let me know if you have any questions 🙌

Joshua Lamorie

@Lisa said

> When the idea reaches 60 votes, we add a Product Feedback status to the post.

Right, that's what I was afraid of. As I summarised earlier, better support for a WBS method of working is the general objective of several (8) forum topics which total 72 votes. Isn't that enough to try to get some planning underway? The WBS concept is fundamental to Systems Engineering project management approach and is used extensively in the aerospace industry.

I appreciate the opportunities to game such a method, but it is not unusual for other issue management/feature request systems (redmine, gitlab, github, bugzilla) used by open source projects to have duplicate feature request entries linked and grouped.

Thanks for keeping the discussion alive. I've already seen the number of votes here go up by 10 in the past few days .

Joe Miller

Lisa,

this has been very frustrating. We are waiting and waiting for the WBS feature. It is VERY IMPORTANT.

It seems a technicality that is causing this new feature to be delayed. The requests are distributed into several threads, but they all want the same thing, a flexible, powerful WBS feature in Wrike.

They may be described a bit differently, and they may be in several threads, but please, escalate this to the production team right away.

It is preventing us from using Wrike fully, and will definitley cause us to look elsewhere if it is not added to wrike very soon.

For a good example of how to implement WBS in a project, please see how Microsoft Project does it. They have had this feature for 10 years or more.

Joe

Jessica Deike

Dear Lisa,

I fully agree with Joe- all requests regarding WBS should be reason enough to let your product team dive deeper into the topic and, in the long run, to keep and satisfy existing customers.

Just asking for a "use case" over and over is pretty much annoying and WRIKE is pushing us to evaluate other tools indirectly.

Thanks for reading.

Kindest,

Jessica

Elizaveta Bogdanova

@Joe, @Jessica I totally understand where you're coming from with this request. I really don't have any updates to share at the moment, but I'll keep asking and I will get back to you if I have news.

Thank you so much for taking the time to share your feedback here, it brings lots of value.