i want to work item will be created in the project when the other one's created in different project. how can I make trigger between to different work items in two different project
Related
Since the process of one A/B test usually takes multiple sprints I would like to add another board in which I can add the A/B tests (as F.E. features). User stories for one sprint can then be added to a specific sprint for my team (which consists of a few specialists and a developer). This way I am able to overview the status (research phase, test , code writing, running, analysis, etc.) of all tests in one overview. I have not been able to find out how this is possiblie within Azure Devops, or if there is a work around. Can anyone help me?
My team also works in projects other than A/B tests, which means we cannot use the boards section.
Unless there is a hidden way to add another board to a team?
You could Copy or clone a work item to add the user stories or tests to a new boards. Open the user story you want to clone, then click Create copy of work item and choose whether to include exist links, attachments and child work items. After creating, change the Area and Iteration to your target boards.
Update
In Azure DevOps you can only create boards by creating a team. The team board is created as a side-effect of creating the team. Please refer to Manage and configure team tools and Configure and customize Azure Boardsfor details.
After creating and configuring a new team, you could see the boards in the dropdown list.
Im happy with the Kanban side of Devops along with dashboards etc. The team is looking to try to roll out multiple projects, but all with the same Epics, Features, Backlog and Tasks etc etc ie a repeatable project. Although im fairly sure the answer is no, is there a way to build out a project with all the work items, and then copy this as a file, and when creating a new one, use this as the basis??
is there a way to build out a project with all the work items, and then copy this as a file, and when creating a new one, use this as the basis??
When you create new projects, you can use the same Process.
For copy the work items as the basis, I suggest that you can export Work items to excel , then when you can import the exported work items to new projects.
For more detailed info, you can refer to this doc: Bulk import or update work items using CSV files
Our team have created new teams under one project. For example we have a project called 2021 and then various teams under this i.e. Q1, Q2, Q3 etc. I have created new teams in 'project settings' --> 'Teams'. But, we would like to be able to customise and have different fields for each team as they may require different information.
I have tried editing the process but cannot seem to do this and cannot seem to make different layouts under the work item types in the process for the project.
Any advice on how we can have separate layouts for different teams under one project would be greatly appreciated. Thanks!!
created new teams
Each project is based on a process that defines the building blocks for tracking work. You can only customize inherited processes. Any changes you make to the inherited process automatically appears in the projects that use that process. They can not apply on a particular team.
You may specify or give an example to describe how you want to different customized fields for the different teams, so that we can see whether there is any workaround.
Within Azure DevOps Server, is there a way to limit the work items that can be tied to a given pull request to only those in the current project? Currently, when submitting a pull request Azure DevOps Server suggests and allows all work items within the project collection to be selected.
Yes there is a way to limit the work items from another project to be selected in current project. You can change the View, create, or modify work items Permissions within an area path. Check Restrict access to view or modify objects
So Let's say there are Project A and B. And Restrict work items in Project B to be selected from Project A. In order to achieve this, you need to set the permissions from Project B. Please refer to below steps:
1,Go the Project setting for Project B --> Click Project configuration under Boards --> Click Areas -->Click the 3dots of the root Areas of Project B --> Click Security
2, In the Search Box search for Project A team(or any team that includes all the users in Project A, if there isnot one, you can create a team in project A to include all the users.). Then set the permission to View work items in this node to Deny.
Then any user in Project A team willnot be able to add the workitems from Project B in a pull request.
Above steps will cause some problem if a user is also in other project team. But you can override the inherited permission for this user by following step 1 to allow the the view permission for this user.
If there are many projects in your collection, you have to set repeat setting above permission for each one of them.
However you can submit a feature request(click suggest a feature and choose Azure devops) that restricting view workitems permission in a Project Level to Microsoft Development team. Hope they will consider implementing this feature.
It is possible to query issues through Github API. The JSON contains all info (assignees, label, milestone, ...) except the project. There is an endpoint to retrieve all projects for a repo but there is no reference between the issues and the project / project cards.
I am trying to consolidate two repos into one and hence I am also moving all issues from one repo to another. I was able to port everything except the issue project assignment. Is there a way to do this quickly? Currently it seems like I have to manually click on every single issue, assign to the project and then move the issue to the appropriate card in the project board.