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.
Related
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.
Presently I am using Devops Azure (Cloud).
For Work items is there a way to add and modify workflow Reasons.
State and Reason change
I am looking to add some custom reasons in the work item for each State.
Is there a way to change these. From the help, its mentioned, "You can add and remove workflow States. However, you can't add or modify workflow Reasons.". Any pointers to do this.
I am looking to add some custom reasons in the work item for each State.
I am afraid there is no such way to add some custom reasons in the work item for each State.
Although we can use custom fields and custom rules, it can only achieve one state for one reason.
That because Azure devops not allowed to have multiple rules with the same action type using the same conditions:
And on the other hand, we also could not add a list as value of Picklist items:
So, I do not believe we could add some custom reasonS in the work item for each State at this moment.
You could add your request for adding a list as value of Picklist items on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
Hope this helps.
There is no any news here. As workaround, you can:
Add a new custom field with a pick list with reasons and mark it as required. Add a picklist.
Use rules to set default values into your new field for each state transitions. Add a rule to a work item type.
Or developers need the Work Item forms as designed for our agile process, but we'd like our regular users to be able to add new bugs and user stories using a simplified form, where a lot of fields are removed and some have team specific default values.
How can this be done?
The closest match I've found so far is templates, where field defaults can be defined, but the form that's used/displayed is still the large cluttered one. Being able to use the template link to land directly on a pre-filled form is a step in the right direction, though.
Azure DevOps allows you to modify your process template and add new work items to your project. You can find the documentation to do this here.
Go to Organization settings for your account --> Process --> Create an inherited process from your process template --> New Work Item Type.
You can then define the fields you want and the layout of the template.
Something else that could be useful in your scenario is the Test and Feedback Extension. This is a simple browser plugin that lets users explore feedback requests and file comments and bugs.
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
I work in IBM RTC (Rational Team Concert); the Project Area I own is built on the IBM Formal Project Management Process Template.
I’m looking for a mean to get work items created programmatically;
I do want when I create a Change Request work item, to allow the selection of different teams and from this attribute(s), create automatically children work items Task directly assigned to the right team/member.
How would you recommend to do so?
Although it is not a direct answer to your issue, but I guess it would help. It's more like a workaround more than a solution to your requirement.
The work around is divided into two steps:
Create a work item template from a CR with all its sub tasks included in the work item template.
Create a CR using the previously created template programmatically.
Note: This means that you'll need to create a work item template for each team.