As is situation:
Projects have a WBS number "001". A subproject has consequent number "001.001" That's great.
Request:
Consequent enumberation of WBS numbers from project to activity.
Example:
- Mainproject has "P.001"
- Ticket has "T.001"
- Activity has "A.001"
- Milestone has"M.001"
Number could be applied out of ID and Prefix "M or T or A or P" could decuced from attribute (T = Ticket, ... ).
- Subproject has "P.001.P.001."
- Activity with parent Activity "A.001" has "A.001.A.002"
- Activity with parent Ticket "T.001" has "T.001.A.001"
- Milestone with parent Activity "A.001" has "A.001.M.001".
- ...
Every item has a unique number. In combination (concatenation) this number will join item to project, request (Ticket) and activity.
Parent construction could be seen in the same manner as "is a subproject of ..."
Example:
Project "003" hast a request (Ticket) "007" and is succeeded by an activity "025", enters in a Milestone "010"
- Ticket: parent is project P.003.T.007
- Activitiy: parent is Ticket T.007.A.025
- Milestone: parent is Ticket = T.007.M.010
WBS exists in Project'Or RIA, but not exactly how you requested.
1) Tickets don't have WBS : only planned elements (Projects, Activities and Milestones) have WBS.
2) WBS do not inlcude type of item (P, T, A, M)
3) WBS is not consistent : it depends on
- WBS of parent element
- order in the list of children element for the same parent
This means :
- if you change the order of one element, its WBS changes
- if you change the order of one element, the WBS of all his children change
- if you change the parent of one element, its WBS and the WBS of all his children change
The only referential integrity is through the id, than is the only data that will never change.
WBS is stored in table PlanningElement (that's why only planned elements have WBS), in two fields :
- wbs = 1.1.2.1
- wbssortable = 001.001.002.001 (to be able to sort items)
the case WBS numbers changing is fine. The way describe to quite OK. Type of item only improve readability.
But I couldn't find any WBS numbers without project overview.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Cookies settings
×
Functional Cookies
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Please login to see yours activities!
Other cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.
Support us on Capterra
