Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I've set up TFS 2012 on a server and am trying to add a user to the Project Collection Valid Users group. I'm trying to do this through the web interface.
When I hit Save Changes it errors with TF50618: The Team Foundation Valid Users group cannot be modified directly.
What I am trying to do is get one user set up on TFS so that I can connect Visual Studio 2012 to it. I do not have any projects set up yet. My intention is to import a VSS repository into TFS.
I think the Project Collection Valid Users to be a read only group. The members of that group are determined by the members of the child-groups. If you want to have another person in that group, try adding them to one of the groups within the scope. As it sounds like an administrative task you are about to do, add your user to the Project Collection Administrators Group.
Later, you are assigning new users to the Team Projects of the Default Collection. The Team Projects are automatically assigned to the Project Collection Valid Users Group.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
i have found a queue build option in Team Founder .. so whats the exact purpose of queue build? we are able to build in vs itself...so just need clarification
You can build projects directly from visual studio, from a command prompt using msbuild - what TFS gives you (in brief) is the ability to set up continious integration, so a build is automatically initiated when a member of the team checks in - and you can hook in mail to notify team members if they broke the build. You can also manage work items, sprints, etc. Well worth the effort in my opinion.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
I am liking JIRA a lot, but we need a CLIENT/PROJECT/ISSUE Schema. Not Just Project and issue. It seems that Projects in JIRA are actually Clients. If you have many clients each with its own projects and issues it seems silly that you cant manage clients. It does so many other things so well, it seems strange.
Some companies indeed use JIRA Project as clients, and use JIRA Components (which are parts of a project) as the projects.
Note that permissions, issue types and other configuration "schemes" in JIRA are configured per-project, not per-component. That means that with this schema you will be able to set up permissions for all issues belonging to a specific client.
Versions are also set per JIRA Project, i.e. per client in this case, which also might not be good.
JIRA also has Project Categories. If you have a small number of clients, you might do better with assigning a client to a project category, and then project will be JIRA project.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
With regards to SharePoint 2007 versioning feature:
Is it possible to put restriction on who can delete the version of a changed item in a SharePoint List?
Can the versioning be apply to new item?
Example: Suppose there are 3 items created inside a SharePoint List, it will be called Version 1. Later, someone add 5 new items into a SharePoint List, this will result in Version 2. So, if the admin notice that the 5 new items are invalid entry, it can simply delete Version 2.
Is it possible to delete certain version for a particular item in a SharePoint List?
Yes. You can customize or create new permission roles (ex. you can customize the contribute role to disallow deleteing items) See: http://office.microsoft.com/en-us/sharepoint-server-help/manage-permission-levels-HA010117209.aspx
Versioning is applied on a per-item basis. So, in your example, each Item would be at version 1 when uploaded. Suppose an item is edited, then checked in and published as a major version. That item is now version 2 while the other items are still version 1. Batch deletes based on version like you suggest is pointless. Instead, just delete the items individually.
Yes. See the answer to #1. One of the customizable abilities is the ability to delete versions.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I'm thinking of giving each part of the agile lifecycle its own project (TFS project, not csproj) as per Microsoft's agile template.
Is it possible to move items (like User Stories or Tasks) from one Project to another?
Does the organization of these projects have any bearing on or affect the actual software build (solutions, csproj, etc)?
What is the recommended organizational structure of Projects, etc for an agile project?
Are there any guides you can recommend for setting TFS up to work with the standard agile process?
Do not set up multiple TFS projects for the same team/product line. You can't move things from one to another and they won't be able to share a common parent source control so you would miss out on much of what source control has to offer. Do some research by reading the links on the other answers.
I have never heard such a strange idea.
You should have one team project for each endeavor. Basically, a team project is the intersection of a team with a project.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Is there a way to associate a single MS Project file with multiple TFS projects?
Here is the situation: I have two projects that are related and have dependencies on each other and I would like to have one MS Project file to coordinate the schedule. But, I do not see how I can associate (publish) to multiple TFS projects.
What I was trying to do is not possible. The correct way to handle the problem is to create a master schedule where multiple project files are linked to a master project file. Here is a video that describes this process: http://www.youtube.com/watch?v=DvJIZ7lCEDw