문제

We are using Team Foundation Server 2010\2012 to manage our requirements. Ours is an FDA audited company. Often someone makes changes to a requirement (user story requirement) after it is in the completed state. This is a red flag. We have added a state called 'Locked'.

The question is how do I disable the save functionality of work item when a particular criteria is met? It would be good to display a message to the user that the requirement is locked and that saving is disabled.

도움이 되었습니까?

해결책 2

The trick is to add another field which would be populated when the State is set to 'Locked'. Using the combination of 'ProhibitedValues' and 'Allowed Values', the field will be set to contain a valid value when a person from 'Key Master' sets the state to 'Locked'. This value for the field would be invalid for all other users. The invalid value in the field will prevent the ordinary user from saving after it is locked.

I would be happy to provide example, if requested.

다른 팁

You can find some useful samples how to achieve this in the Team Foundation Server Process Template Customization Guidance from the VS ALM Rangers

라이센스 : CC-BY-SA ~와 함께 속성
제휴하지 않습니다 StackOverflow
scroll top