I am new to azure devops and devops field. I am exploring myself in azure devops, where learning boards. I I was confused while updating the status of my work item. I was assigned with a task (example: create a login page. Now i went to azure boards and its allowing me to edit the title and priority fields. Those are already set by my higher levels. I only need to add details like time efforts, status). What security is our team missing to achieve this?
Also i need to move the work items from one stage to next stage(Todo to completed) via VS2017. How to achieve that. Now i am currently going to devops portal and drag and drop the workitems to next columns.
If you have permission to edit a work item, you can edit any field on the work item. This is by design. Whether it's a limitation or not is up to you to decide.
You can update the work item state from Visual Studio by linking it to your commit in the team explorer. Refer to the documentation.
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.
I have problem with configuration of AzureDevOps process.
My goal is simply automate work items - when work item changes state to done or is in state done on certain board I want to transfer it on other board.
I tried to achieve this by applying custom rules in my organization. Example:
I navigate to Organization Settings, select Process then I select process from list (is inherited from Scrum parent). Then I select bug (for example) and go to rules tab.
Here is screen of my configuration
Both Board no.1 and Board no.2 exist as Team Projects. I've added clearing assign to field and this one works properly.
I wondering if there is much easier way to automate moving work items through boards or team projects on status change.
I wondering if there is much easier way to automate moving work items
through boards or team projects on status change.
For this issue, I am afraid there is no easier way to achieve this requirement. Azure Devops has provided a built-in custom rule function to achieve this. This is already a very easy way.
In addition, we can also achieve this through the azure logic app, but this needs to be set in the azure portal. I don’t think it will be more convenient than custom rules.
To move work items to another project, you must be a member of the Project Administrators group or be granted explicit permissions to move work items.
I would like to know how to use/move azure boards with activity date to a different organisation project..
If you are referring to moving work items from one organization to another, you can use the Excel to export and import the work items to achieve this .
First, you need to create a query to get work items, then install the Azure DevOps Office Integration Tool in azure devops , in Excel click on the Team button and then New List to get data from Azure DevOps to Excel, and finally publish work items to destination organization.
For detailed steps, please refer to this blog.
In addition, another way is that you could think about using third party extension tool like the Migration Tools for Azure DevOps . You can refer to this similar case.
I'm trying to configure and customize the Azure DevOps tool as per the requirement for my application development team. In the boards setting, I have selected the option "Bugs are managed with Tasks" to get a good view of my sprint items. However, my team reports post production issues as Bugs in the tool and enabling the above mentioned setting doesn't allow me to view these Bugs in the Kanban Boad. Reason is they are not linked with any User Story.
I have been exploring the options in Backlog levels options available in the Processes settings and found that the Backlog level "Stories" is tagged only for User Story.
My query here is can i try linking Bug and Task to the already existing "Stories" backlog level. Azure DevOps does gives option to create a custom backlog level and custom Work item type. I would like to customize the existing functionality to best fit my team. Please let me know if there is a work around.
Query regarding Backlog Levels in Azure Devops
This behavior is by designed and there is no way to fix it at present for the exists Work item type Bug.
Because there is only one requirement backlog and it cannot be removed, but can be renamed and edited:
There is an user voice about this request on the Developer Community.
As workaround, we could create a custom the Work item type and add it to backlog level, for example, I create a custom Work item type BugWithoutTask, then add it portfolio backlog:
Then go to backlog settings and enable new backlog:
Now, we could these BugwithoutTask in the Kanban Boad:
You could check this document for some more deails.
Hope this helps.
what do i need to configure to show on what board column my tasks and bug is located in Azure DevOps. Currently it only displays on Epic,Feature and User Stories only.
It is by design that Tasks and Bugs are not shown with Epics, Features, and Stories in Boards, for Tasks is not of backlog level and it is managed within Stories as child item. For details please check this document.
Hovever you can easily create new tasks, tests and bugs from the a story's board. Please check the document Add a task or set of tasks on Boards. You can check the document for more information about add child items from Backlogs
The operation that is supported by azure devops currently is that you can setup Bugs shown with Epics, Features, and Stories. Please check documents Set your team's preferences for tracking bugs
You can also choose to hide or show one or more backlog level(Epics, Features, Stories) for Backlog navigation. For detailed information please check document Select backlog navigation levels for your team.
If you want to suggest Microsoft to support showing tasks and bugs with Stories and Epics. You can submit a feature(click suggest a feature and choose azure devops) request here.