I have a system that pushes work items into Visual Studio Team Services.
Is it possible to add a user that does not have its own email to the project? So I don't have to use my own user for this service?
All I want is to add a user with alternative credentials who is not a actual person.
No, it is impossible.
To push work items, you need to use a VSO user account which has the Edit work items in this node permission under Area security.
Related
Our organization is using Azure DevOps to for project management. Currently, to track work progress, which tasks are pending, which are done, issues raised etc. in project we give full access to clients, such that they can view activities happening in that project. Now as an organization, we want to restrict client from viewing the activities done by our internal team. We don't want them to view bugs created by our QA Team to developers. We only want them to CREATE & VIEW bugs created by them. Is there any provision to give only those rights to the client ?
Can we give rights for external users (clients) to create bugs and view status of bugs created by THEM only & RESTRICT view of bugs/work items created by internal team team members? Please assist.
Thanks in advance.
Is there any provision to give only those rights to the client? Can we give rights for external users (clients) to create bugs and view status of bugs created by THEM only & RESTRICT view of bugs/work items created by internal team members?
You could consider to add these external users (clients) to be a new team, and then set "View permissions for this node" permission and "View work items in this node" permission for this team to be Deny for specific areas, so the team cannot view work items under these areas. See: Set permissions and access for work tracking for more details.
I have a problem and apparently it happens because before I had my business account registered as a personal account in microsoft. I have already deleted that account to keep the business account only but now when I want to add the account to my organization in DevOps it does not allow me to add it, it tells me that there is an error and already, it does not add it to the organization.
I realized that DevOps tries to add the personal Microsoft account again and not the new one I have (Microsoft 365), I don't know how I can solve that, if they could help me.
The question is also in Developer Community in Microsoft: https://developercommunity.visualstudio.com/content/problem/1096647/no-puedo-unirme-a-una-organizacion-en-devops.html
Solved the issue with these steps below:
Sign out the account and close the browser.
Please ask your Project Collection Admins (PCA) to delete and re-add the account in the organization.
Don't click the email link or use the normal browser window to access the organization.
Firstly, please open an InPrivate/incognito browser window. Then, you could access to "https://dev.azure.com/TCI-Software" directly in the InPrivate/incognito browser window.
When I created VSTS account, mistakenly I have chosen Personal instead of Work,School... (as you can see on the picture)
Now I need to associate it with my organisation account. I search a lot and I couldn't find anything useful.
Please guide me to solve this problem.
Sorry, you can't associate personal VSTS to an Organisation Although both identities use the same email address, they're still separate identities with different profiles, security settings, and permissions.
Please see the Q&A below:
Why must I choose between a "work or school account" and my "personal
account"?
Choose Work or school account if you want to use your organization's directory to authenticate VSTS users and to control
VSTS account access. This limits access to members in your
organization's directory. All other users must sign in with work or
school accounts too.
Choose Personal account if you want to use your Microsoft account with VSTS. All other users must sign in with Microsoft
accounts too.
If you feel annoying about the pop-up, you could just follow the
link to rename your personal Microsoft account.
If you are worrying about the subscribers：
Within the Visual Studio subscriber portal, you may be able to add an
alternate identity--in addition to the identity you used during activation. Today we allow you to add an alternate identity if you
used a Microsoft account to activate your subscription. This way you
can also add a work or school account (which you use when logging into
Visual Studio, Office 365, or your corporate or school network),
allowing you to access VSTS using both your personal account and your work or school account.
Detail steps please take a look at：How to add an alternate identity to your Visual Studio subscription
If you can't sign in when choose both please see: Why can't I sign
in after I choose either "personal Microsoft account" or "work or
school account"?
Check this link to associate your personal account with a organization account.
https://learn.microsoft.com/en-us/vsts/release-notes/2018/mar-05-vsts#subscriptions
We use Visual Studio Team Services backed by Azure AD and want any user in our AD to be able to submit a feature or bug. I know some products like Jira allow this either through their issue collector or via email. It seems with VSTS the user has to be a stakeholder in the project or else they would receive a 401 (I tested with one user in our AD). Has anyone found a good solution or extension that allows AD users (or users external to the project) to submit features requests/bugs to a VSTS project? Or do we have to create something utilizing VSTS's REST API?
The user must be added to your VSTS, then he can submit a feature or bug work item. Regarding personal access token (can call Work item REST API), it is created by the user in your VSTS too, it is not recommended, because of the security issue and you don’t know who submit the feature or bug, it’s hard to manage.
In Visual Studio Team Services, if the sign-in e-mail is changed for a user what will happen? Will work history be retained under the new e-mail address?
Edit: To hopefully clarify, the sign-in email is not the owner of the VSTS account. This is tied to a user who is just a stakeholder.
If you want to change account owner for Visual Studio Team Services, this operation won't affect any history.
If you want to use a different e-mail that no relationship with previous account, that means you need to sign up a new account, then everything will be fresh.