I'm trying to add a new state to the user story Work Item type in VSTS. To do this I follow the instructions outlined here:
https://www.visualstudio.com/en-gb/docs/work/process/customize-process-workflow
However, when I get the states page the "+ New state" option is greyed out and I cannot click on it. I am a member of the "Project Collection Administrators".
Can anyone tell me how to enable the "+ New state" button?
So VSO has this Hierarchy like there are Processes which can be considered as your SDLC ( Agile, CMMI and Scrum). These are System defined processes and we cannot edit them. And Each Process can have many number of Work Items associated with it. System level process cannot be edited meaning you cannot create, edit, create state for a system process. The work around is to create a Inherited Process with the Available System Processes, which will also inherit the Work Items. This inherited process can be edited (you can create, edit, create state for the work items available in this inherited process). So keep in mind while inheriting from any process, for which work work item you want to add state and create a inherited process from that parent process.
Please follow this link to create a inherited process : https://www.visualstudio.com/en-us/docs/work/process/manage-process
Also keep in mind that whatever project you create has to be based on the inherited process so that the changes that you make in the customization is available at the Work Item form level.
Hope this helps.
Thanks,
Bhadhri
Related
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 are using Azure Devops Server. When a bug is created, I would like to create a child task automatically. The task does not need to have any particular properties, it just need to be created with default values and have a default name like "Placeholder" or something like that.
I have already encountered some different ways of doing it, but neither of them seems to be well suited for me:
The extension 1-click-child-links could be used to create a child task by clicking a button in the context menu after creating the bug. This will of course work, but it would be even better if it could be done in the background ensuring the task to be created even if the user forgets to click the button.
As I understand it, using the Microsoft Flow software tasks can be created in the background when creating a bug which would be exactly what I'm looking for, but it would be nice to find a simpler way of doing it without installing a complete software tool.
I've learned that it is possible to hook into different events by using service hooks (https://learn.microsoft.com/en-us/azure/devops/service-hooks/events?view=azure-devops). There are a couple of standard integrations, but neither of them can be used to solve my case. So using this method, I guess I need to develop a custom service creating the task?
Is there a simpler solution to achieve my gool or do I need to stick with one of the solutions above?
As a workaround , we can set Azure Logic App, select When a work item is created"as trigger, and then select Create a work item as action.
Make sure to set the Link URL to the “When a work item is created” URL and set the Link Type to Hierarchy-reverse to create the Task as a child of the Bug item. Please refer to the settings below:
Save the Logic Apps Designer, and then when the bug item is created, the child task named Placeholder will be automatically created.
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.
We're currently using Azure DevOps to manage work items (user stories, task , etc.). I'd like enable an event/trigger when I close the user story, the child task-status are also closed. Is this possible?
I saw within
User Story State Change to Update Work Items
Generally, we would like convert the parent work item state based on the linked child work item state, not the other way around.
Converting the child work item state based on the linked parent work item state may cause some unsafe issue. For example, if we have one child work item that is not completed, then we accidentally closed the parent work item. In this case, the incomplete child work item will also be closed incorrectly.
To resolve auto change parent states, there is a free solution on the marketplace available: TFS Aggregator, For VSTS, you need to use Web Hook to complete it. Please refer to this : https://github.com/tfsaggregator/tfsaggregator-webhooks.
Besides, if auto change the linked child work item states is your final requirement, You can use the Rest API to invoke state changes. You could check the post and the post for some more details.
Hope this helps.
I have two questions about the customization of a process in VSTS
Is there a simple way to make the fields conditionally read-only, visible as simple as we make it required? (simpler than creating a new component)
Is there a way to control the workflow of the new states, to forbid removed items to turn into done without going back to new
Is there an example of gridcontrol, like the test case steps, to download and make a new control.
For your questions:
Is there a simple way to make the fields conditionally read-only,
visible as simple as we make it required? (simpler than creating a new
component)
No, read only (Assign value rules) is not available for VSTS (Inheritance process model). You can only (de)select it as Required or use custom rules to conditionally change the field as read only.
Is there a way to control the workflow of the new states, to forbid
removed items to turn into done without going back to new
There are no such settings/configurations for that. But you can develop an extension for a new Save button to check the work item revisions.
Is there an example of gridcontrol, like the test case steps, to
download and make a new control.
For VSTS work item custom control, you can refer Add a custom control. And it also shows related extension Multivalue control.