I have created my account in Visual Studio Team Services, and added the team members as well. I am able to see the uses got added.
But I cannot see them when I tried to assign work for them. Everybody's acccess level including me, is Basic and I have added them as Project Contributors, and me in Project Administrators group.
When I tried to create a new work item (new feature), on the Unassigned text box, no users name is popping up.
Any idea where I am going wrong? Please provide any suggestion.
The work item control is changed to a MRU control, so people you care about most show up immediately. Since you never assign tasks before, you would see "No identities found" in the drop down:
You can type the user name and then click "Search" in the drop down:
Then you'll see the user:
Related
I just created a list of work items, under a project in Azure DevOps: 1 epic and 3 features (these 3 are child linked to the epic).
But when I go to the backlogs to see these items, they are not shown. I get the following message:
I tried a couple of solutions that I found on the web, but they do not work.
Please help me to figure out why these are not being shown in the backlog... (of course I'm new at Azure DevOps).
Thanks!
From the screenshot, I can see that only epic and feature:
You need to select epic or feature type in this place:
Create Tasks under the User Story.
Epic ---> Features---> User Story --->Tasks. So then in the backlog top right corner when you select Epic, Features, User Story, Tasks will appear. When you select the Feature, User Story, Tasks will appear. When you select the User Story, Tasks will appear.
Reference link
I found the answer by going through the different buttons on the screen:
Go to Configure Team Settings (when selected a box will be displayed)
Be sure that in the Backlog section all items are selected (in my case they weren´t)
Be sure that all of the work items in different levels are shown by clicking on the + symbol. (the - symbol will hide them).
And that is it!
I have created a new Team/Area under our project within Azure DevOps.
When I send the URL for the backlog, the team members are able to access the link but not see any of the work items.
I have tried the following:
Confirm the user has Basic licence.
Confirm the user has access to the project.
Added the user to the Team for that area.
Is there anything obvious I am missing?
I am pretty confident this is not a bug, but just something in the process of giving users access that I am not doing.
Any help very much appreciated.
Thanks,
Alasdair.
When I send the URL for the backlog, the team members are able to access the link but not see any of the work items.
This could be caused by multiple reasons which means we might need to check several setttings.
Choose the right team in BackLogs page:
check the Project Settings-Team configuration-Areas, make sure the target Team area has been added:
Check Project Settings - Permissions and make sure your team has
the right permission to see the BackLogs Itmes.
Is this something that I need to set every time I create a new team?
No, you don't have to set them every time. When you create a team,
the Permissions setting could be automatically inherited:
Azure DevOps Services:
I need to hide all WIs belonging to one of the teams (= their Iteration Path) from the rest of the project.
Yet the team will need to see everyone else's WIs in this project
What is a proper way to achieve that?
set 'Deny' on 'View work items in this node' for all 'Contributors' and 'Readers'? But if my team is in 'Contributors' (so they can see all the other WIs) their access will also be denied (by inheritance), even if i add them explicitly.
Area Path 'Security' settings
I hoped to google a ready solution for such a common request, but have not found one yet, unfortunately.
But if my team is in 'Contributors' (so they can see all the other WIs) their access will also be denied (by inheritance), even if i add them explicitly.
This is actually an expected behavior which you can refer to Permission settings, it says For most groups and almost all permissions, Deny overrides Allow., this means when one of the team members is denied from View work items in this node in one group(such as his team) and allowed in another group(such as Contributors), he can't see the specific team's work items since the Deny overrides Allow.
It's also simple to understand logically, user A will be allowed to see another team's work items when his team is denied from?
My opinion is that you should move the user A to another team which could see the work items in the specific team.
I've run multiple migrations for different projects using the Ops Hub Tool, which have all run without any errors but not one of them sets the "Assigned To" field on Work Items. Is there some configuration trick in order to get the "Assigned To" to be set in Visual Studio Online?
I finally figured this out. The projects had previously been migrated from TFS 2008 to TFS 2012 and at that time the User Accounts were recreated. For various reasons errors were encountered when trying to align the identities so the User Accounts have an identical display name but were for identities that were not valid. The TFS Work Items will display the invalid user in the Assigned To field but you wouldn't be able to edit and save the work item until you selected a valid user.
So for the work items that were still set to the invalid identities (all the historic tasks prior to the initial migration) the Assigned To field is not being set. We had a couple of projects that had not been modified since then (and of course I started with those projects) thus it appeared that Assigned To was not being populated at all. I figured out what the problem was when I moved onto a project with more recent activity.
I have a sharepoint workflow that I created in VS2010, and I've deployed it through the web interface to my sharepoint 2010 environment. The ui says that it's been deployed, and it is activated on my site. If I look in my site features, I do see the entry for it and everything looks good. But when I go to any of my lists to try to add it in, it isn't showing up... it has to be something easy that I'm missing, does anyone have any thoughts? Thanks for the help!
I did finally find what the issue was... for me, when I went to the workflow settings on a list, I had to hit the drop down for item type and choose item instead of all. Once I did that, the workflow showed up for me to select it.
Go to the List | Worklfow Settings page and select the link "Remove Workflow"
When that loads, see if the workflow is set to "Allow New Instances", if not, make it so and see if that gets things running for you again.