I am working with TFS 2018 where I modify the templates of the work items so that they have the data that I need, that is, add new fields.
I need these fields to be synchronized to Project in a particular field, what happens to me is that they are not impacting on project.
Is it possible to do this?
If you mean Synchronize Team Foundation Server with Project Server, then TFS 2018 no longer support native integration with Office Project Server. You need to find the third-party support.
TFS 2017 and later versions no longer support native integration with
Office Project Server. If you upgrade to TFS 2017 or want to use a
third party option, see Synchronize TFS with Project Server.
If you mean Synchronize data between work item fields, then you can apply Assign value rules to a filed, e.g COPY rule : Copies a specified value to a field when a user creates or modifies a work item.
Related
I'm in the process of migrating some source code from an in-house system over to TFS 2015. I'm using the APIs via Microsoft.TeamFoundation.VersionControl.Client etc libraries.
Ideally I would like to also import the history of each item including who made the change and when.
The workspace.CheckIn method allows me to specify the "author" who made the change, but I don't think it's possible to supply the when.
Does anyone know if's it possible to "back-date" a checkin?
You can't change CreatedDate of a changeset. In fact you should not be doing this in the first place.
Even if you manage to change somehow then you will loose the track of when you really created/check in the changeset on TFS.
If you are upgrading older TFS to TFS2015. Which is a full data transfer. TFS sever will also include the back-date changeset. However you are using an in-house system, just the same as checking in code from local development.
So you may have to manually manage the source control history of your in-house system, such as import to a Excel.
we have just upgraded to TFS 2017 from 2013. We had a custom plugin that ran when we changed the build quality. Since the upgrade it doesn't fire. we have tried changing the required DLLs to use the The 2017 client dlls. but the build quality handler does not trigger the plugin. it uses the Microsoft.TeamFoundation.Framework.Server.ISubscriber interface. We do not get any exceptions as well on the tfs server.
The ISubscriber implementation needs to be recompiled against the TFS 2017 Server as well as Client object model.
And it's important to understand that the new build infrastructure (the non-xaml builds) likely trigger a different set of notifications. At least they're not queryable with the old Client Object Model IBuildServer, you need to use the new REST API.
Without knowing more about your setup (what type of builds, the exact versions of the object model you're binding against, what permissions the TFS Service user has) it's hard to tell where this is going wrong. We have a troubleshooting guide for the TFS Aggregator (https://github.com/tfsaggregator/tfsaggregator/wiki/Troubleshooting) which is also a ISubscriber plugin, it may help you debug your setup.
I have been tasked with creating a custom planning view from TFS.
I have a reasonable amount of experience with the TFS Api but I want to try and avoid having to create and maintain a new application for this.
I have looked at SSRS for TFS but I am unable to access all of the data I need (tags etc.) so this is not an option (as it will invalidate support).
I would ideally like to create a "widget" to appear on one of the TFS dashboards but am not sure where to start. The widget would also need to allow access to the TFS api to gather the data it needs to generate.
Please can someone advise where I may look to start or an alternative approach.
You may want to take a look at http://integrate.visualstudio.com where you can find documentation for the TFS API. The REST API works for TFS 2015 and above.
While you can extend the web interface with Extensions (https://marketplace.visualstudio.com/) in Visual Studio Team Services (VSTS), this feature is not yet available in TFS on-premises as of TFS 2015 Update 1.
You can check the published feature timeline for updates, but at this time extensions for TFS are marked as "TBD".
If you're working with TFS2013 + Update2 or a higher version of TFS, it is allowed for Team Administrators to customize TFS dashboard via pinning items to the homepage without writing any code.
For example, if you would like to add a chart into the dashboard, you just need to go to the query’s Charts page and pin it to the home page. See the following image (quoted from this MSDN article)
We are planning to upgrade from Tfs 2012 to Tfs 2013. Can anyone help me understand the difference in process templates between them? We use all three process templates for different projects.
The changes are very minor, except for:
The introduction of Portfolio backlogs.
Test Plans and test Suites are now Work Item Types (TFS 2013 update 3).
The AgileConfig and CommonProcessConfig files have been merged to a single file inside the template
The minor changes:
Git support for the Source Control options
Stackrank type fields are now hidden by default (because Agile task boards are now features of the Standard CAL).
Tag field support through the API.
The easiest way to visualize all differences is by comparing them through the TFS Team Project Manager which can be downloaded here.
TFS 2013 did not work well with our existing workspaces defined on remote network drives. TFS 2012 did work with this configuration.
After working several hours with our System Administrators, we gave up on trying to get the trying to get the existing network drive workspaces to work with the TFS 2013. Converting the workspaces to local drive locations enabled us to work with TFS 2013.
I was setting up a new build definition today and noticed there is an option 'Copy build output to the following Source Control folder'. I don't believe I have seen this before. It appears to me from searching google that it might be new as of TFS 11 (AKA TFS 2012) which I do not have installed on my system (or any system in my company network to my knowledge). My company uses TFS 2010 right now.
I went to another user who is able to view build definitions and it also was present when the build definitions were viewed.
This is what i see:
My questions:
1) Was this a part of TFS 2010 and I am just not remembering seeing it?
2) If this IS part of TFS 2010, how to enable this option (it is disabled).
3) If this is NOT a part of TFS 2010, how did it get there?
Yes, it is part of TFS 2010, but I have no idea how it got here!
I believe this is for those who use TFS 'as a service' (when you
have no file share to copy it to). According to
how-can-i-copy-build-output-to-the-source-control-folder
I have this in TFS/VS 2010 (SP1):