I'm currently working on a project with a small team of 5 users.
I had a users which email address didn't work, so I added a second email address of his, without removing the previous one. The issue with this is, that when I added the second email address, it counted as the 5th free user.
Now that I deleted his unused email address and try to add another 5th free user, it doesn't allow me add him as a contributor anymore, but as a stakeholder.
So basically first I had it like this:
User A
User B
User C
User D
User D2
Then I tried adding user E, but I received the following notification:
NOTE: The user Jef Van Vinckenroye has access to limited functionality
as a Stakeholder. Basic access level is required for access to version
control and Agile tools.
Now I removed user D2 and added E instead so I have the following:
User A
User B
User C
User D
User E
But I still get the same error.
Suggestions? :)
It seems that you are using Visual Studio Team Service not on-premises TFS.
For VSTS, if you haven't paid for any uses, you will have 5 users who get Basic feature and Unlimited users who get Stakeholder features. When there's 5 Basic accounts(email address) added to VSTS, the account after will be set to Stakeholder. These 5 accounts are free.
And if you want to have more Basic users, you need to pay for them. Please refer to this document for more details: https://www.visualstudio.com/en-us/docs/setup-admin/team-services/add-account-users-assign-access-levels-team-services#expando-need-more-basic-users
Update:
Please check the User page and add the Jef Van Vinckenroye set it to Basic Level. Look in my VSTS User page, I have 7 users, 5 Basic and 2 Stackholder. If I add the v-gaxiao account as a Contributor, it will get the error like you. When I change it to Basic at the User page, he could be added to contributor.
Related
My boss come with a very unique requirement, below is the explanation.
Imagine there is 10 user for a particular project team.
And the work flow is like
Documenting -> Review -> Publish
Now, the requirement is like below.
If I create Ticket with Summary "Version 1.0 Documents" with the above explained workflow, then it should also allow us facility to manager for user regarding each state of workflow like
Documenting assign to User A
Review Assign to User B
Publish Assign to User C
Note: I know I can assign ticket to individual user while changing state, but I want something pre-planned so as soon as I change status of ticket it will automatically assign to user.
I know I can do this using post action of transaction but what I want is, the assignee should be specified at creation of ticket as the same workflow going to use by many project and ticket, and every project will have different team
So , I need something add-on which allow me to manage team for each ticket.
Also, User C should be able to see his/her upcoming work if ticket is in any previous state i,e Documenting or review.
I suggest you should create account role for this and group to each department/team for their flow. you can use account role for separating their works then the department/team is useful for which members/users can see the particular issue/ticket. we already build something like this we have 3 account roles each ticket so i can say this is possible. if you still have question just let me know thanks.
I am trying to migrate source control only from a TFS2013 system to VSTS and I have a question about how to manage user migration.
We have been using TFS since it was released and have a >250000 changeset history that we would like to preserve.
We have linked our Azure AD to the VSTS project and I have added in a relevant group that contains most of our current users, but these are not showing up in the user mapping screen presumably as they are not 'proper' users until they have logged on and applied their MSDN license. Is there an easy way of adding around 200 users to the system and applying a license?
Most of the other users that require mapping have long since left the company but it is useful to see which person made which changeset. This class of user will never have an active account on TFS but the current system would force me to remap these users to a current account losing that information. Is there any way of keeping this data?
I can successfully setup a feedback request but I can only add one stakeholder at a time. I thought I'd setup a TFS group and it would send the feedback request to each of the members of that group. No such luck, turns out the TFS groups don't even show on the list of stakeholders in my setup.
TFS Permissions on the group. Please let me know if you need any other information.
What am I doing wrong?
The submitted feedback will be sent to stakeholders via email. There's no email address for TFS group, so it is not possible to select TFS groups as Stakeholders.
You need to:
Create a group in Exchange or mail-enable an existing group in Active Directory, create one email address for the created group. (Check this for the details.)
Add the created Windows Group to TFS, and grand it with the required permissions. (Check this for the details.)
When submit the feedback request, type the group alias created in Step1 and click "Check Name". Then, the group will show up correctly, and requested feedback will be sent to everyone in that group.
I also tried a lot of ways to add a tfs group to stakeholder, but prove to be no way to add a tfs group, stakeholder can only show windows group. You can click "Browse" to select multiple users at a time or add a windows group to TFS group and then select this windows group.
We have a situation where TFS was taken into use when we all had 2 user accounts. We started using TFS with account A but, after a while, found out that account B was better. In the end we want to use the A accounts only for RDP sessions. We would now like to remove all the A accounts from TFS so that we don't make mistakes in assigning tasks to a person.
Deleting the old accounts from the AD is not an option, we still use those accounts for RDP sessions. What we did was migrate all the WI's from account A to account B. Thereafter I removed all permissions for the old A accounts, with in mind that TFS would clear those accounts since they are no longer in use. The double account in the assigned-to field
Unfortunately the old accounts are still visible despite they are no longer involved in any project or group. No rights for the (development) user
How can we remove those accounts from TFS? Maybe there is somekind of cache that needs to be cleared somewhere, or a rebuild of the warehouse?
Thanks in advance!
By Default the Assigned To field shows the list of all Valid TFS Users (this is a specific TFS Group). So if you don't want somebody to show up in that list you have to make sure they are not in the Valid TFS Users group. If you inspect this group in the TFS Admin interface you can see which other groups are members of it. Now it's just a matter of tracing through the many TFS security groups to make sure that those user accounts are not included anywhere that would result in them being part of TFS Valid Users.
Anyone know how to remove users in PlasticSCM when the server is configured to use Active Directory security?
The cm au/du commands are meant to activate or deactivate users.
But users are not 'added' to Plastic as such.
When a user does an operation in Plastic, it will be automatically added provided you have enough licences and the user has permissions to access the system (you've set the correct ACLs).
Suppose you just have a 20 users license:
You simply install the license (copy the plasticd.lic file)
Then the first user access the system, it will be 'activated'
Second user accesss, second 'activation', it happens automatically
Then suppose you already have 20 developers using Plastic and one of them leaves and a new one enters, then you have to deactivate the old one and activate the new one, but only then.
Hope it helps.