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.
Related
We have two fields Fix Versions and Affects Version in a bug wherein the drop down values are to be auto populated based on the tags created in Azure Repos. For ex: if there are tags v1.001.560, v1.001.561 etc and for any new tags created, the tag version should appear as a drop down value for these fields. Is there a feasible approach to achieve this? Please suggest.
In short, there is no method to meet your needs now. As a suggestion, you could submit a suggestion ticket to suggest the feature on: https://developercommunity.visualstudio.com/report?space=21&entry=suggestion. That will allow you to directly interact with the appropriate product group, and makes it more convenient for the product group to collect and categorize your suggestions.
DevOps only supports setting to specific values for your custom picklist fields. Please note custom field is used to support tracking data requirements you have that aren't met with the existing set of fields.
Besides, to realize your idea, we should auto populate tag values to the field when opening the work item. However, we also not have such a trigger even though getting the tags with Rest API.
Is is possible to make a custom rule in Azure DevOps that either shows or hides a field in a work item depending on a condition?
For example:
Condition 1: When a work item is created
Action 1: Hide field X
Condition 2: When work item state changes from Active to Resolved
Action 2: Show field X
I hope someone can help :-)
For Azure DevOps, we can only Create and manage inherited processes to customize the fields/rules.
To hide fields/groups, for some of the existing fields/groups (default fields/groups) we can directly hide them from the layout. For customized fields we can only remove them from the layout.
What you need, there is no such build-in option to achieve.
You could submit a user voice here: Azure DevOps Feature Request
I would like to add some custom fields to a Azure DevOps Project.
By default, there are only two fields available: Name and Description.
However, I would like to add additional information to the project like internal ProjectNo, OrderNo, OfferNo, Offer Date and so on.
Is there a way to do this?
As far as I'm aware there isn't any way to custom this aspect currently. You could always add it as a suggestion here; https://developercommunity.visualstudio.com/spaces/21/index.html.
Alternatively, depending on what you are looking to accomplish and how you want to use these new fields, could you make these 'projects' Epics (or create another Work Item type) under a 'global project'? If so you can easily customise work items to include these fields.
I am working through creating a custom process in Azure DevOps and was curious if field values from parent can be shared with child items.
Here is an example:
Create field 'Custom Field 9' on Epic work type
Create the same field 'Custom Field 9' on Product Backlog Item work type
Create an epic and fill in the value of 'Custom Field 9'
Create a child Product Backlog Item, 'Custom Field 9' is then inherited to the backlog items field.
What I've tried so far is to use a rule on either Epic or Product Backlog Item, however, I do not believe the rules can apply to creation of children processes.
One other option I'm going to try later today is a Flow that detects when a child work item is created and perform it automatically. I'd like to try to keep this contained to Azure DevOps if possible.
Edit: Thought it helpful to mention that we are using the hosted solution of DevOps and nothing on premise.
Sorry to say that as default, there does not such a work item features with "out of the box". But you can use another tool to achieve this.
Like you said, Microsoft Flow, there does not such feature supported while connect with Azure Devops.
But, in addiiton, I think you can do this with writing some custom scripts. And then configure Web hook to trigger this custom events.
Also, here has another tool named TFS Aggregator (Web Service) to achieve what you want. You can set and configure apply certain rules (such as copying fields from a parent item to a child item). And it will trigger after a work item is created or saved.
I know this is very inconvenient, here has an same feature suggest which raised by others. They has the same demand with you. You can vote and comment for this suggestion. When there are enough communities vote and add comments for this feedback, the product team member will take this feedback seriously.
I needed this feature as well, but in it's absence I have got it to work (relatively easily) with an Azure Logic App (for anyone also using Azure)
Trigger
When a work item is created
Then
Get work item details using "Parent" as the work item ID to search for
Finally
Update the new work item with any field from the parent you require
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.