We are using Azure Devops Server and I have added a custom state called Tested to User Stories and bugs using the Witadmin tool. I have also added transitions to all other possible states. As you can see belo, my customized state is displayed perfectly in both the Bug form and the User story form.
But as you can see below, there is no way for me to map a Kanban board column to my customized state:
Is there somehting I have missed or is it not possible to map a board column to customized states?
Try to export ProcessConfiguration definition with command witadmin exportprocessconfig and update the RequirementBacklog section for the WIT you modified. Specifically, make sure that the Tested state you want to have show up on the Kanban board to type="InProgress":
<State type="InProgress" value="Tested" />
Then use witadmin importprocessconfig command to import the ProcessConfiguration definition.
Related
For context, I just read this question Creating Issues on Board in Azure DevOps from API
I have the exact same goal, except the solution didn't address it enough in my opinion because it didn't create the element inside the board.
I am using https://learn.microsoft.com/en-us/rest/api/azure/devops/wit/work-items/create?view=azure-devops-rest-5.1&tabs=HTTP, It works great, however, I cannot send my item in a specific team board, it always end in "Work Items" menu, did I miss a field or something ?
That depends on your board.... as an example, for Agile you have to create User Story, Feature, or Epic.
Additionally, check your team settings (Define area paths and assign to a team)... if it uses custom settings for Area Path, you have to add Area Path to your request body.
I am currently using devops (cloud) services. I have created a custom Work Item Type (WIT) within an inherited process from Agile. I would like to configure it to behave like exactly like Agile's User Story WIT. By this I mean:
The WIT should be addable in the taskboard view of the Sprints (see first pic, WorkItemTaskBoard).
One should be able to add tasks to the item just like User Story's.
The WIT should rank below features in the WIT hierarchy. This way when it is added as a child of a feature it will be visible in the Backlogs view (see second pic, BacklogChildMissing)
According to my reading I need to export my inherited process as an XML, edit said XML then import the modified XML. I have two issues with this.
A. I have not found any reliable documentation how to perform the above.
B. Although I am using cloud based Devops (dev.azure.com) and am the organization owner I do not appear to have rights to import a process (see third pic, ImportProcessMissing)
Can anyone confirm that I need to perform the export, edit, import the XML as specified above in order to achieve 1, 2 and 3? If so, I would need help in figuring out how to import the process.
WorkItemTaskBoard
BacklogChildMissing - The WIT is not displayed despite being a child of Test Feature.
ImportProcessMissing - Import button is missing.
You can follow the steps like as below image shows to configure the customer WIT in the inherited Agile process.
Create the custom WIT.
Set the custom WIT as the Stories backlog level.
After above settings, in the project which is using the inherited Agile process, you can manage the custom WIT like as User Story.
See below example:
We have a typical board with the following columns.
New
Groomed
In Dev
Ready for QA
In QA
Ready for release
Released
When we click and drag a user story from one column to another, we'd like it to update the "assigned to" field automatically depending on which stage its in. We're not seeing any settings from which to accomplish this from the Azure DevOps UI. Any suggestions?
You could customize the Process to achieve what you want:
Customize States for each column in user story work item type (The process for your team project should be an inherited process). Go to the Organization Setting -- Process, choose the inherited Process your team project used, and then choose user story work item type. Click States tab and add appropriate states for each column. Check the following example:
Add rules for user story work item type. Click Rules tab, and add following rule for each State:
I'm using Azure DevOps Service (the on-line version, not on-premise) with Agile methodology.
I'm trying to add a custom state of 'Testing'. I use the method described here, but this doesn't seem to work. I can add Testing as a column in the sprint board, but it doesn't appear in the State picklist values (I do understand that adding a column will not add a State).
How can I get this to appear in the State picklist?
How can I get this to appear in the State picklist?
1.You can quickly navigate to the process your current project belongs to via Project settings => Overview => Project Details.
Then you can modify the states there. If you want to add a Testing state to Bug WorkItem type, click the Bug and click the new state:
2.And we should know that only inherited process can be modified in this way. So we must make sure our project is created from inherited process. Otherwise the New State button is disabled.
I am comparing Jira against Azure Devops Board and notices few limitation:
1. Components field
JIRA - Components are sub-sections of a project; they are used to group issues within a project into smaller parts. Components add some structures to the projects, breaking it up into features, teams, modules, subprojects and more. Using components you can generate reports, collect statistics, and display it on dashboards and so on.
To add new components, as shown in the above screen you can add name, description, component lead and default assignee.
DEVOPS BOARD - No component field, even if we can customized to add one, it is just a String.
2. No Issue-Type Prefix Ticket ID
JIRA - We can customized to have an issue key, -. For example : REQ-1313
DEVOPS BOARD - Just a number.
3. Workflow Sequencing
JIRA - We can use workflow properties for changing the order of the sequence of transition buttons. So from "Ready" state, we can either go back to "New" / "In Progress" / "Rejected" but not "In Testing"
DEVOPS BOARD - Seems like we can jump to any state we want.
I'm not sure if I'm misconfigure, but if so, please provide a way to do so, or maybe an alternatives to limitations listed above.
Thanks!
1. Component field
Azure DevOps uses the Area Path field for that purpose. About area and iteration paths (aka sprints), Define area paths and assign to a team
2. No Issue-Type Prefix Ticket ID
I can not understand where is a problem here? Can you describe some example?
3. Workflow Sequencing
You can restrict change of the State field with rules: Prevent reopening work item once closed