I was just trying to work out if it was possible to add validation to Work Item fields in Visual Studio Online / Team Services.
My use case is i want to make some fields mandatory if a certain condition is met (e.g. if Field1 = x then Field2 cannot be blank)
There isn't any way to do this. To achieve this feature, you need to customize the process template and work item definition which is not supported by VSTS for now.
There is already a feature request for this on VSTS User Voice: Customize Process Template on Visual Studio Online and MS keeps working on this. Refer to this link for details: VSTS Process Customization futures (January 2016)
Related
I'm looking for a way to add an additional column for test steps in Azure DevOps TestCase WorkItem.
It is possible to add new fields (string / select controls etc) and reorder existing fields on the test case level. But is it possible to customize the Microsoft.VSTS.TCM.Steps Field?
There is no possibility to adapt it in the test case edit view
and the field delete / edit in all fields area is deactivated too
In the self hosted azure devops server 2019 it seems to be possible over tfs power tools / wit export & import. But how to do it in the azure cloud? maybe there is a way over extensions?
It seems you are using XML process model in azure devops server 2019. But in azure devops service, you are using inherited processes model. To customize work item types in inherited processes, please refer to the following link:
https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/customize-process-wit?view=azure-devops
You can only delete the custom fields, those fields defined for system processes can not be deleted. Steps is a particular field that can not be hide. If you want to customize Steps field, you would need to create a custom work item and customize the Steps field there.
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 want to create a query with my followed works items in TFS 2017, but I didn't find the field name for the followed state.
I want to create that query in order to add a new widget in home dashboard.
Is it possible to make a query with your followed items in TFS2017?
No, there isn’t the feature to create a query with followed work items in TFS or VSTS and pin to dashboard. You just can check followed work items from Work>Queries.
I submit a user voice here (Query for followed workitem and pin to dashboard), you can vote it.
You can achieve this scenario by creating a custom Followed work items query (System.ID In #Follows) and saving it to Shared Queries. Then, simply pin the query to your dashboard as a Query Results Widget and anyone who views it will see their followed work items (similarly you can pin an Assigned to me query using the #me macro and users will see items assigned to them).
The #Follows macro has been around in VSTS for awhile and was introduced in TFS 2017. Check out our documentation on queries macros for more information.
As proposed by Lauren, in TFS 2017, you can build an ad-hoc query "ID In #follows" (Field=ID / Operator=In / Value=#follows). The results will be similar to the Default Query "Followed work items" under Work>Queries.
However, I was never able to save this query: trying to save always got me an error "TF212023: You cannot compare fields with different data types in the WHERE clause of a work item query. The error is caused by «[System.Id] in (#follows)»."
What I found out is, that the query works well in the web interface, but cannot be run nor created or edited in Visual Studio.
I did not even find a way to "follow" a workitem in VS, this seems to be available only in the web interface as well.
Updated SharePoint 2010 workflows do not work until iisreset.
I am using:
SharePoint 2013 with CU's updated through May 2015
SharePoint Designer 2013 32bit
Procedure:
Create a new list with two columns Title (default), NewText (single line text )
Create a SharePoint 2010 list workflow using SPD2013. The workflow is set to run manually only. Its only action is to put text into the NewText field when it runs.
Create a list item
Run the workflow manually - It works fine
Edit the workflow in SPD2013 to simply put different text in the NewText field. e.g. initially the text was "FirstTry" changed to "SecondTry"
Check for Errors (none of course)
Publish - no errors
I look at the workflows for the list and see that the original workflow was replaced as expected. (The new workflow is listed with the original workflow listed with (Previous Version . . . .) after the name.
Run the workflow on the item - the text DOES NOT change.
Create a new item
Run the workflow - the text is set to "FirstTry" NOT "SecondTry"
Recheck the workflow in SPD, republish etc. no change
Do an iisreset - now the workflow sets the text to "SecondTry" as desired. further changes continue to have the problem as described above.
I have tried this on multiple site collections, list, different fields etc
I have tried the suggestions from others on this. The most common is clear %LOCALAPPDATA%\Microsoft\WebsiteCache. This does not work for me with no change is symptoms.
Other suggestion was to create the WF as a SharePoint 2013 workflow. Although this seems to work OK (I actually have a different problem with this) it is not a final answer because there are times we need to use SP2010 workflows. An example is that SP2013 will only use SP2010 workflows as a workflow approval action. Also SP2013 workflows do not provide a start approval process AND all of the OOTB workflows are based on the SP2010 workflows.
We really need to be able to update the SP2010 workflows - obviously iisreset is not a solution.
I am pulling my hair out on this one. Help!! Please!!
I got this answer from TechNet Community it appears to work.
I recommend to enable versioning in workflows list and then check if the issue still occurs.
Open SharePoint Designer > click All Files > right click Workflows under All Files tab and select Properties > click Administration Web Page button in the menu > click Versioning Settings in the browser.
Here is a similar thread for your reference:
https://social.msdn.microsoft.com/Forums/office/en-US/a63a1894-6b1d-420a-95dd-b6c546eab34d/updates-made-to-sharepoint-designer-2010-workflow-do-not-show-up-on-the-server?forum=sharepointcustomizationprevious
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.