We are currently testing out TFS2018 to upgrade from 2015. As there is no 2018 Process Editor it seems the 2017 version is the one to use. Without changing the WITs the format is radically different. Most noticeably the tabs in the WIT are no longer working and display totally differently by being sort of being expandable. The other part of that means the HTML entry field are all listed on the main WIT screen as opposed under the tabs or their replacement expandable sections but the other fields are there.
The 2017 editor shows them the way they were in 2015 but once in TFS 2018 they display differently. Any idea of what the issue is?
TFS 2017 introduced a new work item layout, and TFS 2018 made it mandatory. You'll have to adapt to the new layout and adjust things accordingly.
Related
I'm trying to add work items from TFS to Visual Studio in the below hierarchy as they are in TFS. Anyone know how to do it?
- EPIC
- Feature
- Requirement
The My Work panel in Visual Studio does not support any hierarchy view. It is a small and simple section with the brief work items description. Just try to imagine a query result with 10 child levels in that window ))
You have to use the Work Items panel and the Queries section.
Unfortunately, this is not available at present.
If you use the new work item tracking with Visual Studio 2017 and above, you may have noticed that work items now open in a browser window by default.
To ensure compatibility with the new process customization capabilities, new controls and the new Work item form options, just you keep Visual Studio open work items in the browser.
So we encourage users to track work items in web portal. Work items in Visual Studio is used to do some simply track. There is no structure to how the work items are listed. Your requirement could not be achieved now. Sorry for any inconvenience.
We currently have a TFS 2012 Server which is being replaced by a 2015 server, the aim is to gradually migrate our code from one to the other.
When we do this we would like to maintain the checkin history, labels etc, Looking at similar questions the answer seemed to be to use the integration toolkit, however it looks like it (and its successor the integration platform) do not support TFS 2015.
We are using TFVC rather than git, if that makes a difference.
I don't have much knowledge about the integration toolkit, but I would actually suggest to do the upgrade one Team Project Collection at a time, but moving them separately to a new server with TFS 2015 installed. This way you will keep all history, label etc.
We have done this way back when upgrading from TFS 2010 to TFS 2013. Only obstacle that we had was a collection around 500 GB in size so it took around 16 hours for the upgrade to finish.
The following answer specifies the steps needed to move a collection to another server:
Copy TFS 2012 collection to another server with TFS 2015 Installed
We have used this Migration tool for our Client.
It’s possible to migrate TFS 2012 data to TFS 2015 with all information intact without any system downtime. The premium version of OpsHub Visual Studio Migration Utility (OVSMU) supports migration of projects with TFVC repository from one instance to another. It supports the 2010, 2012, 2013, and 2015 versions of TFS and all versions of Visual Studio Online, including the 2017 version. Along with basic data, you can migrate all workitems with history, comments, attachments, relationships, and source control with changesets, history, labels, comments, etc. You can checkout the details here: https://www.opshub.com/products/opshub-visual-studio-migration-utility/
I setup TFS 2013 scrum template late last year and was using it without issue. When adding a new PBI or BUG on the Web Portal and tabbing into the Assigned To field I was able to start typing or drop down the list to see all the members of the Team Project.
After upgrading to TFS 2015 the list is gone and type ahead does not work. If I type the first few characters of a member and click search I am able to find a member, but this is cumbersome when going through and trying to quickly add a PBI or BUG. FYI this also happens when adding a new Bug as well as tasks on both a PBI and Bug.
we are about to upgrade to TFS 2013 from TFS 2010. And are having some problems with our process templates.
We are today using Urban Turtle with 2010 and we want to upgrade to the 2013 version of urban Turtle.
We have tried and gotten the process template to work in a clean 2013, but I am unable to find good information on what changes is needed to get the new "features" workitems and such to work in Urban Turtle 2013 and our custom Template.
My thought is maybe try downloading a clean 2010 process template/config for urban turtle and a clean for 2013 and then try compare the files for changes and then try to apply them manually to my custom template.
Is that the way to go or is there a good guide or so on what changes to make to the process template to get it to work?
Edit:
Thanks for the tips! Pasting all workitem changes is a lot (custom workflows, custom workitems, ..) so I rather not do that.
My main problem is as said the Urban Turtle part. They have this new "feature" workitem but we have an epic work item that is very similar. I want Urban Turtle to handle our epics as their "feature". I understand that how to do that depends on how my epic implementation is.
But my goal with this post was to get an answer with some good guide or information other than manually comparing the XML of the versions. so the question is "Is there any guide or information on how to upgrade process template to the 2013 Urban Turtle?". I don't need a solution for my specific template just some information.
I have managed to remove weekends from the sprint burndown chart within the TFS report server however cannot get the change to reflect on the Web Access view.
Following some documentation online I have even made changes to the 'Sprint Burndown.rdl' report within the Scrum 2013 Process Template and uploaded this back into TFS however this didn't appear to change anything.
Has anyone managed to successfully remove weekends from this chart?
The Web Access module uses a different location to store what weekdays are and which aren't. You cannot remove weekends from the graph, this is a much requested feature and according to the admin comment it is coming soon.
UNDER REVIEW · Visual Studio team
Visual Studio team (Product Team, Microsoft) responded · Aug 22, 2013:
We’re starting work on this and should be able to close it down soon. Stay tuned.
It might ship with TFS 2013 update 2 if they managed to fix this.
Update
TFS 2013 update 2 RC now has the features to set Team Days off, which will effectively hide the weekends and these team days off from the burndown chart.
Non-working days – Starting with Update 2, you can define you’re non-working days (weekends, for most of us) and we’ll exclude them from the burn down calculation so it no longer looks like you are on track when you really aren’t (because you don’t plan to work the weekend :)).
http://blogs.msdn.com/b/bharry/archive/2014/02/05/vs-tfs-2013-2-update-2-ctp-released.aspx