Each new "version" ("state") of a versionable gets a new (unique) ID.

The source control object that contains a set of logically related
changes (new versions) is called a "change set" (it's what shows up in
the history view, the pending changes view, etc.).

There is an object called a "link" that connects a work item to a change
set object. This link relationship is many/many, so one work item can
be linked to many change sets, and one change set can be linked to many
work items.

When you modify the changes associated with a work item, that can modify
the change sets, and can add/remove link objects that connect change
sets to that work item, but does not produce a new/modified state of the
work item object.

Cheers,
Geoff


jafarkofahi wrote:

Hi Geoff,

Since Workitems have changes (e.g. code changes, bug fixes..etc)
affecting the current project version. Is there a "version"
number associated with workitems (as source files has revision numbers
in SVN).

Hope this clears my question

Thanks
Jafar

gmclemmwrote:
Not sure what you mean by "revision" and
"belong". Could you expand a
bit on your question?

Cheers,
Geoff

jafarkofahi wrote:
Hi,

Is there an attribute that would give me to which revision the work
item belong too?

Thanks
Jafar

Not sure what you mean by "revision" and "belong". Could you expand a
bit on your question?

Cheers,
Geoff

jafarkofahi wrote:

Hi,

Is there an attribute that would give me to which revision the work
item belong too?

Thanks
Jafar