Task ordering in Project 2007

[bking48]

We're just started running Project Pro 2007/Project Server, and need some
help with either a bug, training, or best practice recommendations in
regards to task ordering.

First question is, out of the box without any custom fields or WBS numbers,
should the ID field denote the order of the tasks, or should the WBS, or is
there another 'master' field that denotes the order of the tasks?

We have a project on the Project Server that got it's numbering confused.
One day the project was fine, the next day we opened it off the server and
the ID field is out of order. If we sort by ID, the tasks are not in the
same order as they were saved. For example, putting the tasks in proper
order results in an ID order of 75, 98, 99, 97, 100, 76. The WBS numbers
are also messed up and have duplicates, for instance 3.23.7, 3.23.8, 3.23.1,
3.23.1, 3.23.4, 3.23.1, etc. We realize that we can sort and permanently
renumber the tasks, but that only helps if the new sort order is correct.
Is there a way to not sort, but renumber the tasks? Are ID numbers
calculated each time a project opens? How can we force the WBS numbers to
recalculate and remove the duplicates?

Thanks for the help. We're mainly concerned about getting the task order
back to what it should be if this numbering debacle happens again, or
someone sorts the tasks by say a date field and then saves the project.
FWIW, we did have blank lines in our project, but have now removed them.

Bryan

 

[Jim Aksel]

The numbering debacle is a known and documented problem. Microsoft is
working it.
Here is a link for additional information. The most common cause seems to
be blank lines. I have never been able to duplicate the problem here, but
the number of posts on this topic is large.

https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=255404&SiteID=235

--
If this post was helpful, please consider rating it.

Jim
It''s software; it''s not allowed to win.

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project

 

[bking48]

Thanks, Jim. For my own education on how numbering should work, should the
ID number should always stay with a particular task, unless you add a task
above it, and the WBS numbers should increment properly and stay in order?

 

[Miaplacidus]

Make sure you don't have some filter on. If you are only showing some of the
tasks the numbers will appear out of order.

 

[Jim Aksel]

TaskID and WBS will change as tasks are added above the task in question.
WBS will also change with level of indenture.

If you seek a constant value to be associated with a task, use the UniqueID
field. Once a task has been created, it contains a UniqueID that never
changes.
--
If this post was helpful, please consider rating it.

Jim
It''s software; it''s not allowed to win.

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project