Prevent specific users from modifying area and iteration in a Work Item Type

It is not supported to add READONLY or FROZEN rules on the System.IterationPath and System.AreaPath.

A work around is to create a custom field named "You cannot change this field" for example. Give it the Integer type.
In the "Rules" tap, add one WHENCHANGED rule for each field you want to protect.
In the first one, select System.AreaId in the Field Condition, and navigate to the Rules tab.
Add two rules:
  • COPY
    • For: the TFS group containing the users not authorized for change
    • From: value
    • Value: leave empty
  • REQUIRED
    • For: the TFS group containing the users not authorized for change

Do the same for the second WHENCHANGED rule for System.IterationId

Basically, the following sequence will trigger when an unauthorized user tries to change a protect field (System.AreaId and System.IterationId linked respectively to System.AreaPath and System.IterationPath) :
  • The field value is changed to blank
  • The field is set to REQUIRED
This triggers a validation error when the user modifies the Area or Iteration field. The error message is not the best because it says:
     Field 'You cannot change this field' cannot be empty. 

At least it gets the job done :)

Comments

Post a Comment

Popular posts from this blog

Create a draft release and start it using the TFS REST API

The code below uses the preview API to retrieve a release definition, create a new draft release from the latest build, update some variables, then activate the release and start the deployment on a specific environment. It serves as a reference regarding how to use the RM API. I used the following nuget packages: <packages>   <package id="Microsoft.AspNet.WebApi.Client" targetframework="net452" version="5.2.3"/>   <package id="Microsoft.AspNet.WebApi.Core" targetframework="net452" version="5.2.3"/>   <package id="Microsoft.IdentityModel.Clients.ActiveDirectory" targetframework="net452" version="3.14.1"/>   <package id="Microsoft.TeamFoundation.DistributedTask.Common.Contracts" targetframework="net452" version="15.118.0-preview"/>   <package id="Microsoft.TeamFoundationServer.Client" targetframework="net452"
Read more

Adding a delay before processing Textbox events

Typical scenario: You provide the user with a TextBox he can use to type a filter over a big chunk of data that takes a lot of time to process. Most of the time, you would handle the TextChanged event of the TextBox and issue a filter operation over the data source using the character(s) available in the TextBox. Typical problem: The user complains because he has to wait between the key strokes even if he already knows a filter that would allow the search to take place in a matter of a few seconds. Solution: Introduce a delay between the last key stroke and the processing using a timer. Walkthough: Create a new Winforms project with a Form. Add a TextBox (named textBox), a ListBox (named listBox). To mimic a very slow data source, we will create a dummy class: public class VerySlowDataAccess { private static string [] data = null ; static VerySlowDataAccess () { data = new [] { "AAAAAA1" , "AAAAAA2"
Read more

Change the deployment URL of a ClickOnce application

I use ClickOnce everyday for several internal applications. Recently, I had to move the publishing website to a new host. Here is how you can acheive a completely transparent move without annoying your users or forcing them to uninstall and reinstall the application. First, you need to publish the deployment files on the new server. The deployment configuration is as follows : Publishing folder : URL on the new server Installation Folder : URL on the new server Updates Folder : URL on the new server Revision : last revision + 2 (very important) Then you need to deploy a new version on the old server with an updates folder on the new server. This way, next time the application launches, it will get the new version from the new server, and voila. Here is the configuration for the last deployment on the old server : Publishing folder : URL on the old server Installation Folder : URL on the old server Updates Folder : URL on the new server Revision : last revision + 1 (very important) E
Read more