K
Kerry Saylor
In Project Server 2003/WSS sites, there is a confirmed problem with the list
numbering scheme currently being used by Microsoft. We noticed the problem
with the ISSUE ID column not numbering sequentially as new issues were added.
Example:
New issue created - Issue ID is 1
New issue created - Issue ID is 2
Issue ID 1 is edited 3 separate times
New issue created - Issue ID is 6
This inconsistancy raised questions with our project managers. They were
asking "what happened to issues 3, 4, and 5? After conversations with
Microsoft, each edit increments that Issue ID number, thus, throwing off all
future issue ID's.
We are looking for a way to create a sequentially number our columns so that
they appear 1-2-3-4-5 and so on. I've thought about a calculated field, but,
Microsoft documentation indicates that it is not possible to calculate
information based on different rows.
Is there another way to get these results??
Thanks!
numbering scheme currently being used by Microsoft. We noticed the problem
with the ISSUE ID column not numbering sequentially as new issues were added.
Example:
New issue created - Issue ID is 1
New issue created - Issue ID is 2
Issue ID 1 is edited 3 separate times
New issue created - Issue ID is 6
This inconsistancy raised questions with our project managers. They were
asking "what happened to issues 3, 4, and 5? After conversations with
Microsoft, each edit increments that Issue ID number, thus, throwing off all
future issue ID's.
We are looking for a way to create a sequentially number our columns so that
they appear 1-2-3-4-5 and so on. I've thought about a calculated field, but,
Microsoft documentation indicates that it is not possible to calculate
information based on different rows.
Is there another way to get these results??
Thanks!