Am getting following error while adding standard process templates.
FYI, we upgraded to TFS 2015 from TFS 2013. This projects have customized workitems in TFS 2013.
TF400917: The current configuration is not valid for this feature. This feature cannot be used until you correct the configuration.
Learn about how to correct your configuration
Details about the validation error appear below:
The following element contains an error: PortfolioBacklog(Microsoft.FeatureCategory). TF400522: The following value is not a valid work item category: Microsoft.FeatureCategory. You must specify a valid category.
The following element contains an error: RequirementBacklog. TF400522: The following value is not a valid work item category: Microsoft.FeatureCategory. You must specify a valid category.
The following element contains an error: TaskBacklog. TF400522: The following value is not a valid work item category: Microsoft.TaskCategory. You must specify a valid category.
Thanks in advance
If you just add custom WITs and change the form layout. The Configure Features Wizard will update your team projects and you’ll get access to the latest features.
If you change the workflow or renaming a WIT,then it might require you to perform some manual operations when updating your team project.
More information, see Maintenance and upgrade implications (TFS).
Related
When create a connection using PluginRegistration, I was getting the error below.
'PluginAssembly' entity doesn't contain attribute with Name = 'packageid' and NameMapping = 'Platform'.
Can you offer a solution ? Thank you.enter image description here
Recently Plugin Registration Tool added new features and if the user used to connect has not a System Administrator role errors can happen.
I don't know if it is related to your case but I will check the roles first.
Also XrmToolBox has a Plugin Registration Tool (you can find it inside the Tool Library) you can try with this version and see if you can connect or not.
I'm a tester and my manager has add new team project to the TFS and add my user and a developer user for this team project, when I've tried to add any type of work items the list of "Assigned To" shows all the users correctly, except for the "bug work item" only, I can't assigned to any user and shows that it is not in the list of supported values.
how can I solve this problem?
First, make sure the work item that you're manipulating currently in a state that has a valid transition to New. Otherwise, you will not be able to save the changes.
If you have customized the bug work item type. According to sounds like a rule in the bug workflow or field.
If you run the [witadmin exportwitd] command and export the bug work item type, look for the Assigned To Field and look at the rules on the field. Also take a look at the section and look at the rules for the transitions.
Also take a look at this similar question on TFS2015 Bug/Task unable to assign it to someone else than the user that creates it, try the suggestion mentioned in the link:
needed to give the relevant global top-level permissions for everyone
to view stuff
Just run the below in order to grant the needed rights :
tfssecurity /a+ Server FrameworkGlobalSecurity GenericRead
> "[DefaultCollection]\Project Collection Valid Users" ALLOW
> /collection:http://tfsserver:8080/tfs/DefaultCollection
I am trying to start a build from Powershell using the TFS 2015 REST API. I am sucessful in starting a new build using REST API after following the Post.
Now i am trying to pass some custom parameter that appears in the Build def parameter through the REST API.
I am not sure whether it can be done, if anyone has any previous knowledge please help.
I am using TFS 2015 and XAML based build.
There is an optional option with REST API for querying build called parameters :Parameters to pass to the build. This is optional. If not specified, the default variables for the definition will be used.
Example:
"parameters": "{\"system.debug\":\"true\",\"BuildConfiguration\":\"debug\",\"BuildPlatform\":\"x64\"}"
More details please refer the document from MSDN: Builds
Does anyone know how to create a branch using the VSO Api. The documentation for Branches doesn't include a "create".
I have been experimenting with doing it via the ChangeSet Api without much success.
This is TFVC, not Git.
Just as what you see in "Branches" page, there isn't any way to create branch with the Rest API. And mostly, you can only read/get the information with the Version Control API for now.
I would recommend you to use Client Object Model Reference if you want to manage the Version Control programmatically. To create a branch, use the "CreateBranch()" method in Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer class.
The REST API apparently does allow one to create branches.
The confusion is that people think that this would be a PUT operation on the Branches endpoint of some kind.
It is not.
In the REST API, a branch is just one more kind of change that is checked in as part of a changeset.
It took me a long time to discover this, myself; and I was using the old SOAP API in the belief, shared by everyone else it appears from what I can find in Q&As on the WWW, that this wasn't part of the REST API.
Of course, using the SOAP API prohibits using .NET 5, because the assemblies only come for .NET Framework.
An abandonware API on an abandonware runtime is not a satisfactory way to talk to source control. ☺
The terrible Azure DevOps documentation gives no clue as to this, except for 1 obscure not-even-a-complete-sentence hidden in a minor class: "List of merge sources in case of rename or branch creation."
The only other clue is what appears in the JSON, from a get changeset changes, that describes the changeset of an already-made branch.
The (also abandoned) Azure DevOps sample code does not contain examples for even deleting an item, let alone branching.
Changesets are checked in via the changeset creation endpoint.
The individual change is a TfvcChange in the changeset's list of changes where:
the version control type (which is a set of flags) contains the branch flag; and
the merge source for the change specifies the source item and the range of changeset numbers.
Branching an entire tree appears to be a matter of branching the directory and all of the files and directories in the directory.
In C♯ or PowerShell, this is a TfvcChange with a VersionControlChangeType of Branch, in a TfvcChangeset passed to TfvcHttpClientBase.CreateChangesetAsync().
I am new to WIX. I am using util:PermissionEx for creating ACLs. I can successfully set rights like read, write, read & execute but I am unable to find any information about setting Modify Permission.
I have tried using "Append" attribute to achieve this functionality (this seems to be the only attribute that may do the desired)
But using this, the following compilation error appears:
"error CNDL0004: The util:PermissionEx element contains an unexpected attribute 'Append'."
Could you please help me out in this. Thanks.
My question, and answer-to-self at WiX Permissions, how do I express 'Modify' in terms of DACL flags may assist in some way in terms of mapping the simple right Modify to specific rights.
Looking at the doc, the Append attribute definitely seems to be permitted - what build of Wix [3] are you using? With the latest version, you should be able to remove util: and Ex from your tag as it all seems to be natiuvely supported now. Other examples also show an Extended attribute, which is not accepted by newer versions.