Add a comment. Active Oldest Votes. By default the packages which source control needed are not as part of SSMS. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
Post as a guest Name. Email Required, but never shown. The Overflow Blog. Who owns this outage? For more information, see Kanban features and epics. We are giving you more control of the additional information that shows on the cards on your boards. You can now select annotations that you want to view on your Kanban cards Figure 9. Simply unselect an annotation and it disappears from the cards on your Kanban board.
The first two annotations to show up here are child work items tasks in this example and the Test annotation. For more information, see Customize Cards. We have added a new command to all rich text controls on work items that lets you clear all formatting from selected text.
If you're like most users, you've probably been burned in the past by copying and pasting formatted text into this field that you cannot undo or clear. Personalize your Kanban boards by setting filters on users, iterations, work item types, and tags Figure These filters persist so that you can view your personalized board, even when you connect from multiple devices.
Team members can also filter their boards to view progress accruing to a specific parent work item. For example, a user can view user stories that are linked to a feature, or view work across two or more features that roll up to an epic.
This feature, much like Checklists, is one more step in our effort to bring visibility through to the different backlog levels. For details, see Filter Kanban board. When you create a new work item from the Queries tab or from the New Work Item dashboard widget, the iteration path of that work item is always set to the current iteration.
This is not what all teams want, because it means that bugs could show up on the task board immediately. With this improvement, teams can choose the default iteration path a specific one or the current iteration that should be used for new work items.
Navigate to the administration area for your team to choose a default iteration. For more information, see the Customize area and iteration paths page. You can now add a checkbox control to your work items Figure This new field type Boolean has all the properties of normal fields and can be added to any type in your process.
For details, see Customize a field. You can now add and remove tags from multiple work items using the bulk edit dialog Figure For details, see Add tags to work items.
We have exposed a new extension point on the backlog. Extensions can target the pane on the right side, where mapping and work details are today Figure We have significantly improved the formatting and usability of work item alerts, follows, and mention emails sent by TFS Figure Emails now include a consistent header, a clear call to action, and improved formatting to make sure the information in the mail is easier to consume and understand.
Additionally, all these emails are being designed to ensure they render well on mobile devices. For more information, see Work item alerts. We added the ability to create rich work item templates directly into the native web experience Figure This capability was previously very limited in the web, and only available in this new form through a Visual Studio power tool. Teams can now create and manage a set of templates for quickly modifying common fields.
For details, see Work item templates. Team Foundation Server and later versions no longer support Project Server integration. We have detected that you have Project Server integration configured for this database. Team Foundation Server has made improvements on multiple widgets, such as the Query Tile and Pull Request widgets. We have redesigned our widget catalog to accommodate the growing set of widgets and deliver a better overall experience Figure The new design includes an improved search experience and has been restyled to match the design of our widget configuration panels.
For more details, see Widget Catalog. The Query Tile widget now supports up to 10 conditional rules and has selectable colors Figure The Pull Request widget now supports multiple sizes, allowing users to control the height of the widget. We're working on making most of the widgets we ship resizable, so look for more here.
The New Work Item widget now allows you to select the default work item type, instead of forcing you to select the most common type you're creating over and over from the drop-down list. We have made the WIT chart widgets resizable.
This allows users to see an expanded view of any WIT chart on the dashboard regardless of its original size. We have updated the Team Members widget to make it easier to add somebody to your team Figure Teams can now configure the size of the dashboard's Query Results widget, allowing it to display more results.
The Sprint Overview widget has been redesigned making it easier for teams to see if they are on track. The Assigned to Me widget helps users manage the work assigned to them without leaving the dashboard context Figure By providing a widget dedicated to this purpose, team admins can add this functionality to their dashboards with 16 fewer clicks, no context switches and no typing required.
Users can now view, sort, filter, and manage the work assigned to them within the widget context. The APIs also let you add, remove, update, replace, and get information on a widget or a list of widgets on a dashboard. The documentation is available on Visual Studio online docs. Non-admin users can now create and manage team dashboards. Team admins can restrict non-admin permissions through the dashboard manager.
For more information, see Dashboards. Some major changes have been made in Git for Team Foundation Server Included are a redesign of the Branches page and a new option to "squash merge". The Branches page has been completely redesigned.
It has a "mine" pivot that shows the branches you created, pushed to, or favorited Figure Each branch shows its build and pull requests status, as well as other commands like Delete. If you know the name of your branch, you can search to find the one you want quickly. For more details on branches, see Manage branches. The pull request experience has some major updates this release, bringing some really powerful diff capabilities, a new commenting experience, and an entirely refreshed UI.
For more details, see Review code with Pull Requests. When opening a pull request, the new look and feel is evident immediately Figure We have reorganized the header to summarize all the critical state and actions, making them accessible from every view in the experience. The Overview now highlights the PR Description and makes it easier than ever to give feedback Figure Events and comments are shown with the newest items on top to help reviewers see the latest changes and comments front and center.
Policies, work items, and reviewers are all provided in detail and reorganized to be more clear and concise. The biggest new feature in this release is the ability to see past updates made to a pull request Figure In previous previews, we released the ability to properly track comments as a PR is updated with changes.
However, it's not always easy to see what's between updates. In the Files view, you can now see exactly what changed each time new code is pushed to your PR. This is very useful if you've given feedback on some code and want to see exactly how it changed, isolated from all the other changes in the review. The new Updates view shows how the PR is changing over time Figure Where the Files view shows how the files have changed over time, the Updates view shows the commits added in each update.
If a force push ever happens, the Updates view will continue to show the past updates as they occurred in history. Use the full power of markdown in all your discussions, including formatting, code with syntax highlighting, links, images, and emoji Figure The commenting controls also have a more user friendly editing experience allowing multiple comments to be edited and then saved at one time. It is now easier to add and remove reviewers from your pull requests.
To add a reviewer or group to your pull request, simply enter their name into the search box in the Reviewers section. To remove a reviewer, hover over their tile in the Reviewers section and click the X to remove them Figure The traceability between builds and pull requests has improved, making it easy to navigate from a PR to a build and back. In the build details view for a build triggered by a pull request, the source will now show a link to the pull request that queued the build.
In the Build Definitions view, any build triggered by a pull request will provide a link to the pull request in the "Triggered By" column. Finally, the Build Explorer view will list pull requests in the source column.
Pull requests in VSTS have been improved to show comments left in files on the proper line, even if those files have been changed since the comments were added. Previously, comments were always shown on the line of the file where they were originally added, even if the file contents changed—in other words, a comment on line 10 would always be shown on line With the latest improvements, the comments follow the code to show what the user expects—if a comment is added on line 10, and two new lines were subsequently added to the beginning of the file, the comment is shown on line Even after the code has changed to shift the line with the original comment from 13 to 14, the comment is appearing in the expected place on line 14 Figure Teams that are using branch policies to protect their branches will want to check out the auto-complete action.
Many times, the author of a pull request is ready to merge their PR, but they are waiting on a build to finish before they can click Complete. Other times, the build is passing, but there is one reviewer that has not given the final approval. In these cases, the auto-complete action lets the author set the PR to automatically complete as soon as the policies are all approved Figure Just like the manual complete action, the author has a chance to customize the message of the merge commit and select the appropriate merge options Figure Once auto-complete has been set, the PR will display a banner that confirms that the auto-complete is set and waiting for policies to complete Figure When all the policies are met e.
As expected, if there is a build failure or the reviewer does not approve, the PR remains active until the policies are passing. When completing a pull request, you now have the option to squash merge Figure This new option produces a single commit containing the changes from the topic branch that is applied to the target branch.
The most notable difference between a regular merge and a squash merge is that the squash merge commit will only have one parent commit. This will mean a simpler history graph, as any intermediate commits made to the topic branch will not be reachable in the resulting commit graph. You can find more information at Squash merge pull requests.
Build status success or failure is now clearly visible in the Code Explorer and Commit Details views Figure More details are just a click away, so you will always know if the changes in the commit passed the build or not. You can also customize which builds post status in the repository options for the build definition. Additionally, the latest changes to the Commit Details view provide deeper insights about your changes. Fixed some bugs.
February Update New "Get Check In file date from comments in Source Safe converted projects" option allows to turn back retrieving Check In file date from comments for Source Safe converted projects. This behaviour is now off by default. Fixed System. Fixed error handling for some TFS errors. Error reporting feature for sending error messages.
Fixed merge list in Merge from Sources function. This state is now detected and error Message is displayed. This TFS error " The Team Foundation server to which your team project is connected does not support querying merge relationships. Icon change function is now applied also on items in Branched folders. Added disabling Branch command if file is new or deleted. Added disabling Destroy command if file is new, move or branch pending. Fixed BUG in File move function.
Files in tree can be selected, after clicking OK button are on all selected files executed Merge operation in TFS unmodified files are ignored. Branch function is used e. Further Merge function is used to applied changes back to common share location.
If we need update all files in project that has multiple files branched from various locations we can use exactly this function Merge from Sources. In the file list on the left side of Source Control Explorer window are branched files displayed with changed icon. Icon is displayed at files that are target of Branch operation or if file is branched only to one location.
If file is branched to more than one location its icon is changed to icon. Dragging with left mouse button executes Move action to the target folder. Dragging with right mouse button opens context menu with Move , Branch and Copy options.
Move and Branch options perform above described functions. Copy option creates file copy to local workspace location and add file from this location to the source control. This option permanently removes files or folders from Source Control. It can be called for multiple items selection, on existing files or files previously deleted with Show deleted items option on. Source Control changes and fixes.
0コメント