WBS order, WBS and level on planned task table

dhanu3
Kilo Sage

3 weeks ago

We need detail description of how WBS order, WBS and level is calculated for Planned task table.

Whenever we create new record for Product, Release, Enhancement, testing task, etc.(all planned task tables)

the WBS order, WBS and level is updated OOB.

We have observed that, if we create multiple release under same product, then WBS for release records in increasing by 1, i.e. if 1st release WBS is 1 then next release WBS is 2. So, based on parent WBS is getting updated.

We wanted to know what is the expected behavior. If WBS is not correct then what all are the issues that we have to face. And how to fix WBS if it is not correct for any record?

 

 

Thanks!

 

 

0 Helpfuls
  • 274 Views
1 REPLY 1

phil_bool_unifi
Kilo Sage

3 weeks ago

Hi @dhanu3 ,

The WBS - work breakdown structure - value is one of the different ways ServiceNow tries to keep the items inside a project in an order that reflects the order in which the tasks need to be handled during the Project.  It's a complex engine, and it does a lot of really useful processing.  Personally, I've not relied on the WBS to order Release records, as I typically populate mine from a epic or from stories, rather than as part of a project flow, but this is clearly supported in the platform.  

 

Adding 1 for each new record that is not a child of the previous record is how ServiceNow keeps project tasks apart, and sorts them into order.  It sounds like this functionality, managed from the Planned Task table, is applying correctly here.

 

In answer to your question, what you're seeing seems to be the expected behaviour.  Is it causing you any issues?  If so, we'd love to help.

0 Helpfuls