I have very recently started working on Team foundation server and really have limited idea on the subject.
I have been given a problem to solve and I really dont have an idea to proceed.
We are doing a TFS-Sharepoint 2010 integration.
In dev server, the TFS is configured and is pointing to TFS_DefaultCollection database. Now, in TFS, 3 new fields have been added. It points to Field101,Field102 and Field103 columns(I dont know how these columns are created but it seems it is dynamically generated,I suppose, not sure though) of WorkItemLatest table.
Some custom stored procedure is written to insert/update the database table with sharepoint webpart. Now in the stored proc, the developer has referenced Field101,Field102 and Field103 columns.
Now comes the question of deployment this to production. In production, there is already a TFS configured. We have to make changes on top of this. But, when running the sql scripts, we found, naturally, Field101,Field102 and Field103 are not present there. So, what should be our approach which will help us address this issue? Please suggest. Also, please let me know how these 3 fields are created when 3 fields are added in TFS UI? Please help.
You need to use the WITAdmin tool to export the work item type definitions that you want to edit and mahe the changes there. You can find this fully documented on MSDN: http://msdn.microsoft.com/en-us/library/dd236914.aspx
Related
We migrated our TFS 2017 to TFS 2018 by first using the "Move or Clone Team Foundation Server from one hardware to another" instructions (https://learn.microsoft.com/en-us/tfs/server/admin/move-clone-hardware) and then upgrading that to TFS 2018 which seemed to go just fine. TFS works, however the URLs in the emails that go out regarding work items are still pointing at the old server. The only URL that I can find to change is the Public URL on the Application Tier, which is already correct. In the message header on the emails that are sent out, the old server also appears to be the sending domain:
In-Reply-To: Tfs.WorkItem.Project.######oldservername
I can't find references to that old server anywhere though. Any idea what I might be missing?
We were able to find the issue. The tbl_AccessMapping table in the database for the Project Collection had different values in it than the tbl_AccessMapping table in the tfs_teamfoundationconfiguration database (specifically the accesspoint field). tfs_teamfoundationconfiguration was correct, so we synced those correct values over to the Project Collection database.
This took some time to take effect, I assume due to caching. Restarting IIS would likely fix it quicker.
I have an old setup with a tfs2010 and sql2008 and the current Collection is holding 3 team Projects. Now i want to create a new team project but for some reason i cant. it seems that it has something to do with the SQL Reporting that dosent excists. i get an error TF218027.
Ive been going through the setup and im wondering a bit
What exactly does the TFS use the reportServer for (MSDN dosent seem to want to tell me)
is there any way to create a Team project without the reporting
Will it damage my excisting data if i create and connect to a new sql reportServer
Hope someone will take the time to give an answer
thanks.
I have already tried the different approtaches discussed on different threads and im primarily looking for information on the 3 questions written above
Try the steps below:
In browser go to: http://application-tier/Reports/Pages/Folder.aspx
Press Folder settings button in the toolbar
Press New Role Assignment button in the toolbar
Specify user name in Group or user name field, check Content Manager role and press OK.
So for the people that actually read the question the answer is.
Keeps track of agile work progress
yes and its actually easy. go to the reporting service and stop it and then tell TFS not to report under reporting
Since it was never running the answer here is No
I don't seem to be able to export tfs work items along with their details, is there any way to do this without using TFSIntegrationTools? (I cannot install these at my work).
Specifically I want to be able to export the Description portion of the Work Item details:
e
If all you need is the work item data then I would design a flat query, run it and then open it up in Excel. You can modify which columns are visible. Once open you can save it off or print or form a report in excel or what have you.
Your other options are to query the warehouse in sql server or query in code.
http://blogs.msdn.com/b/sunder/archive/2010/03/02/reporting-in-team-foundation-server-part-7-excel-reports-from-work-item-queries.aspx
I had the same problem, but I could not benifit from excel, because I wanted to send the list to someone who doesn't have access to the local TFS. So I created a tool to help with that.
In case this helps any one, here is the link to download release one excutables from codeplex https://tfsworkitemsexporter.codeplex.com/
please also feel free to copy the code and edit as you like
I have been developing an application in Visual Studio Lightswitch (Silverlight client in VS2010 SP1 if it makes any difference), and so far have done all the database development in the Lightswitch designer.
I now want to use an external database, but don't want to recreate the whole app, or even just the screens. I have scripted the database, and have created a copy in SQL Server, but can't find out how to get Lightswitch to use this external database without starting the whole thing again.
Is there a simple way to change the connection string so that I can carry on from where I am, but have Lightswitch point at the external database instead of the internal one?
Turns out this is a very difficult thing to do. Super Lightswitch-hacker David Baker saw a post I'd made on the subject in the MSDN Lightswitch forum, and kindly offered to have a go at it for me. It took him several goes, but we got there in the end.
I wouldn't recommend this to anyone. I would strongly recommend using an external database right from the start. I can't see much benefit from using the internal one, and if you ever need more control over it, or want to switch to an external one, you've got major problems.
Hope this helps someone.
You must publish your project in order to create a new SQL database , publishing your project will create DB scripts for your new DB , don't use the internal LS DB to create script for your new DB.
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.