I'm trying to import work items from TFS to VSTS. I have some work items that are assigned to a group that won't import. I recreated the group in VSTS, but when I try to import excel gives me an error:
The identity value 'TriageGroup' for field 'AssignedTo' is an unknown identity.
Triage group is not an AD group which is why VSTS can't assign to it, but it never was in the old TFS world either. Any ideas? Is it possible to import WIs assigned to a group?
There should be some customization made for the WIT Definition in your TFS server what allow the group to be assigned for Work Items. But for VSTS, there isn't any way to customize the WIT definition for now. That means you cannot assign the work item to group in VSTS. You can only assign the work item to an valid user.
Related
At Microsoft documentation we have following section: Automatically include code reviewers
There are two guides:
Default selected that is how to automatically include code reviewers by Browser at your Azure DevOps project repository
The other option is to do it through Azure CLI that is the case that I am asking
At the first guide you could find that we are allow to 'Add people and groups to Reviewers.' BUT at the guide to do it through Azure CLI there is nothing about being able to do it with parameter '--required-reviewer-ids'
I wanted to know if it is possible to do it giving ADO Team identifier value to --required-reviewer-ids and this will take in charge to add every team member of this group
I wanted to know if it is possible to do it giving ADO Team identifier
value to --required-reviewer-ids and this will take in charge to add
every team member of this group
Yes, you can pass the Team id to the --requried-reviewer-ids flag to the cmdlet az repos policy required-reviewer create. once the team is added as a reviewer it will trigger an email to all the members in the team when there is any pull request.
We have tested this in our local environment it is working fine.
Here is the sample output for reference:
I'm new to Azure platform. I'm trying free trial and creating a CI/CD setup for docker by following from the below link.
https://www.azuredevopslabs.com/labs/vstsextend/docker/
I have no issue until setting up build definition. I'm getting below issues when doing changes in the release definition.
when i click on "Authorize" button in azure subscription, I'm getting below issue.
Please let me know what mistake i am doing.
well, the text says it all. you are trying to create a connection with a name that already exists. you need to call it something different or rename the existing one
I have created a new service connection and mapped in the release definition.
Click on Manage link
Click on New service connection button
at top right corner
Select Azure resource manager
Once you select the respective option and click Next. Enter valid name and select respective subscription and resource group details.
How can you get the Azure automation script for just a single service?
In this case I've selected an App Service Plan, but when I click on it's "Automation script" in the Azure Portal, I get the script for everything (minus the various resource types "that cannot be exported yet" )
Unfortunately, export function only allows to export everything in the resource group, so you get an ARM template that represents the resource group.
If you want to get an ARM template solely for that resource, please deploy it into it's own resource group and then use the Automation script option.
Alternatively, you can use armviz to get a visual representation. When you click on a particular element, it will take you directly to that object in the arm template. Not exactly what you are looking for, but might give you enough.
You can't export just a single resource if there are multiple resources in the resource group, but maybe visual studio can help.
If you export the template and load it in VS as an arm template project, you can easily delete the other resources from the sidebar and leave just the one you need. You might also need to clean up the vars/params though.
In our organisation we recently moving to git, I have created a group accidentally I would be appreciate if there is a way to delete this group.
In the most recent version (Mar. 2019):
At top bar, click on Groups.
Type part of the name of the desired group or click on Explore Groups. Click on the desired group.
Go to Settings > General
Expand Path, transfer, remove
At the bottom of page you find Remove group. Click on the button and type the name of the group to activate Confirm button. Then click on Confirm to delete the group.
On the recent version (per posting date 11.4.4) navigate to your group's
Settings > General > Advanced > Expand
There you will find the Remove group button.
The group deletion has changed with GitLab 14.8 (February 2022)
Delete groups at the parent group level
In this milestone, we’ve worked on one of the initial steps to reach feature parity between group owners (in any installation base) and administrator-only functionality that exists solely in the administrator panel for self-managed users.
Group owners can now delete a group and its subgroups from the parent group level. Until now, group owners had to go into each individual group to delete them, which was timely and inefficient. Group owners can now view all groups and delete them from a single place.
See Documentation and Issue.
Note: GitLab 15.4 (September 2022), but only the non-free version, comes with:
API support for immediate group deletion
You can now use the API to immediately delete individual subgroups. Prior to this release, you could only delete individual subgroups from group settings in the UI.
See Documentation and Issue.
Using the latest GitLab API, I checked the project team members of a just created project in a group... and it's an empty Array which is returned
#git_repo_client.team_members(19)
-[]
Previously to this test, I created a group and added members ( master permission so they can create projects in this group )
Then I created projects inside this group
why these group members are not set as project team members ?
should I also add them via the API ? or did the project team methods are deprecated in this latest version GitLab 7.10.1 d5c71c8
thanks for feedback
finally, I decided to duplicate the group members into the project team members within my script ... seems to be 2 different sets