Thanks Nik.That is what I was looking for.While going through the documentation, I couldn't find the relationship between Workspace/Project to Features, Epics, and Themes.
Is there a better Domain Object model that links the Features to the individual Projects?Thanks,Buelent
Hi Buelent,There is no particular relationshiop between workspace/project and Features beyond the fact that the Feature has to exist somewhere. You could imagine the project hierarchy a bit like the filing system on your hard drive and the Features as files that need to exist somewhere. Each work item artefact (Task, Story, Feature, etc., etc) has to exist somewhere in the Project hierarchy. The fields on the artefact type exist for all these things, but they might not be immediately obvious from the API docs. The reason for this is the 'hierarchy' of the types.
If you go to "Artifact' in the WSAPI docs, you will see Project field. However, Artifact is a child type (think of inheritance in object oriented programming) of a WorkspaceDomainObject. This type has the field Workspace.So, to work up from Feature you would go: Feature -> PortfolioItem -> RankableArtifact -> Artifact ->WorkspaceDomainObject -> DomainObject -> PersistableObject. This means that a Feature has all the fields of all those object types.To get a graphical feel for this chain of types, you could install this custom app of mine: https://github.com/nikantonelli/TypeDefinition-Hierarchy