I'm attempting to create a process template, and I'm wondering if there is a way to create/store project level attributes. For example, a project would have a client, maybe some billing information, but it would only need entered once per project. Any help is greatly appreciated.
Project Level Attributes
Hot Topic
- GenericApplication and GenericEndPoint
- "CreateWorkspaceTask" -- FAILED.
- A Minor fxCop Bug??
- DoNotExposeGenericLists - Does this make sense?
- Work Item task via Infopath or Webpage
- Team Explorer doesn't respect filesystem encryption settings
- List of Controls in the webpage
- Unable to add existing unit tests to a solution
- c++ auto increase version and drop folder
- Add classification field to Bug work item type
VS Team System
- password
- GenericMethodsShouldProvideTypeParameter false positives
- Can't Remove "greyed" out files/folders in VS 2005 Beta 2.0 Team Foundation Server
- Reporting completed work per person returns false data
- TreeView automated checking
- Multiple iteration fields in a task.
- Test data for Team System which shows how it should work
- Ignoring certain DependentRequests return codes..
- Messages Suppression
- Error while Building a Setup Project
Project Level Attributes
Bernard Normier
I would suggest that you create a special Work Item Type. You could define it with a couple of fields: "Property Name" and "Property Value". Your template could create several of these records during Project Creation to hold the default values.
You could limit who could create these records by also creating a secure node in the Common Structure Service to hold them. Limit access to Admins or some other group. Then set the Area Path field to this CSS node during the creation of the Type. And don't allow it to be changed (you can do this by using the ReadOnly property in the definition of the Control in the FORM section).
The biggest problem I see is that all users will see your work item type on the menus for adding work items. They could in fact choose to create a new one from the menu. That's why you would have to restrict this somehow.
You should also create a Query that allows users to quickly get to the properties and shows the name and value.
I hope this idea helps,
Jason