everyone.
Is there any way of prevent some users change the Iteration Path field? I'm using TFS 2017 on premise. I'm trying to use the rule READONLY for certain TFS groups, but I'm getting an error that this is not supported for this field.
Any ideas would be really appreciated.
No. If a work item can be edited by a user, any field is eligible to be changed.
You cannot change the behavior of the area path field, as it is a system field.
Related
I'm working with TFS 2013 and VS2013 to modify a work item template but there are some issues I cannot resolve.
I want only the person who is assigned to a work item to be able to modify this. Is there any opportunity to set a general rule for this? I already tried to set each field readonly if the authorized user is not equal to the assigned user. But that didn't work for me, I suspect this is because of the difference between display name and system user (domain).
I also want to create a custom action, which automaticly changes the "assignedTo"-User. Unfortunatly I didn't find any proper guide how to define a custom action. Most guides explanes where an action is refered in a transition, but not where it is defined. Do you have any suggestions where to find such kind of guide?
We have an existing text field 'Defect Found Version' (DFV) and a new Field I have created 'Defect Found Version Picker'
I have made the Picker mandatory & that works fine, listing all the cersions on the project.
The DFV field is set to 'Optional' on the right hand side of the Configure Field layout page, however next to the name on the left there is the text REQUIRED & I can not see how to disable this.
Even if I remove this field from all screens I get an error when I create a bug saying that DFV is required.
Any thoughts please ?
Look at the Field Configuration Scheme used by the JIRA project. Then look at the field configuration used for that issue type. That's where it is being made required. Unless it's because of the JIRA Behaviour plugin, so check if that is active
Do you have take a look on your Workflow validator ?
Sometimes, it's required on your workflow, and not on your screen.
So, we are using TFS 2012 RC and have modified the work flow a bit for a regular task item by adding a few custom transition states.
When updating tasks though Visual Studio 2012 RC, everything works fine. I can move through all the states without any problems. However, when updating the task through TFS Portal, either by dragging the item on the board or opening the form and changing the state using the pulldown, I get the following error: "TF237165: Team Foundation could not update the work item because of a validation error on the server. This may happen because the work item type has been modified or destroyed, or you do not have permission to update the work item."
This ONLY happens, however, when moving to the Done state and nothing else. All other states work fine.
So, I'm not sure what that means since it works fine in Visual Studio. What would be helpful if I could see the exception or more information somewhere, but I don't know where these validation errors are stored.
Any help would be greatly appreciated!
The issue was with the work flow. The transition was setting a field that was conflicting with the state also changing the same field.
In my case there was another issue.
The problem was that the field had a trailing \r\n in the data being sent down by the server. I believe the client javascript OM was removing this which makes the field dirty even though it’s read only.
Workaround was to make the field read-write instead of read-only. Then I set back it to read-only - and now it works.
Micrsoft promised they may fix it in next release.
In my case, on TFS 2013 U5 I had changed my TFS Profile DisplayName so that it did not match my ActiveDirectory DisplayName. I could not edit or create anything until I changed the DisplayName back.
TFS stores information about who created or who activated a work item and for some reason checks its validity whenever the work item is modified.
When a user is deleted from active directory or renamed in active directory, all work items even slightly has connection with the user can not be modified. Usually the error message is something like ...
TF20015: The field 'Activated By' contains the value 'blah blah blah' that is not in the list of supported values.
I've found a blogpost which recommends tweaking the TFS database, which is something not supported nor recommended by Microsoft.
What can be done to resolve this?
Thanks...
e-mre
Caveat: I'm not sure that this will work, and right now I'm not in a position to test it. However, I've had success with this approach on some other fields.
If you use the TFS Power Tools to edit the work item type definition, you should be able to change the Activated By field's rules and add an ALLOWEXISTINGVALUE rule to it. This might allow you to save those records when the AD name changes.
We've used this with some success with the Assigned To field.
I've seen this behaviour. It occurs if someone who activated a work item is removed from Active Directory (leaves the company) or if they change their name (gets married).
It's simple to fix, you just need to change the work item status from Active to Pending then back to Active this will change the "Activated By" field to the person chaging the status and the problem will be resolved.
Are you using TFS 2008? I seem to remember that this issue is fixed in 2010 (but I might have dreamt that)
If you have a lot of work items this blog might have a solution that helps automate the fix.
I've just set up TFS2010 and connected VS2010 to it, then created a New Team Project using the default Agile template. No worries to that point. Then I tried to add a Task. It wanted a value in Title, so I supplied one, no problem there. But then it reported
The field 'Changed By' contains the value 'login-name' that is not
in the list of supported values.
By login-name I mean the name between the single quotes is my Windows Domain login name. I can't even make a guess at a valid value, because this is not a value the user supplies. It's not even displayed on the UI.
When I try to save the Task, I get this
---------------------------
Microsoft Visual Studio
---------------------------
Save failed.
TF20015: The field 'Changed By' contains the value 'pwone' that is not
in the list of supported values.
TF20015: The field 'Activated By' contains the value 'pwone' that is not
in the list of supported values.
---------------------------
OK
---------------------------
Am I incompetent at using this? Is there some configuration I have failed to set? Help! Help! I'm being repressed!
To make things even more confusing, a day later and the whole thing mysteriously works. Neither workstation nor Sharepoint server has been rebooted to the best of my knowledge. It's all too weird for words.
Within TFS there is a job that synchronizes usernames from Active Directory to Work Item Tracking for users that have access to the server. It populates the available values for the Assigned To, Changed By and Activated By fields.
It's possible that this job had a problem or hadn't run yet, which is why it mysteriously started working again the following day.
If it happens again, you can download the Team Foundation Server 2010 Power Tools from here. Then install the Best Practices Analyzer (BPA) component and then run a health scan. It should identify what the problem is.