Azure DevOps Server 2020.1 新增功能 (TFS)

Azure DevOps Server 2020 (原名TFS) 1. 概述Azure DevOps Server(原名TFS)是微软研发管理平台产品,是实现软件运维一体化(DevOps)的实施方案,是敏捷开发方法论在研发团队中的落地工具,是微软研发大数据管理系统。根据企业当前软件研发管理的实际情况,结合Azure DevOps Server的自身功能,可以协助企业在软件质量和开发效率上实现双提升,可以建立起规范统一的研发流程。通过建设基于Azure DevO... 阅读详情

1. 概述

自2005年开始,微软在VSS的基础上发布了TFS(2019年开始更名为Azure DevOps Server)的第一个版本TFS 2005,后续陆续发布了2008/2010/2012/2013/2015/2017/2018/2019/2020,每个版本都会给用户带来令人兴奋的功能。
同样,微软即将发布的Azure DevOps Server 2020 Update 1也为我们带来了一波与软件研发项目管理最新的功能,本文下面的内容就摘录这个最新版本的主要功能。

Boards

State transition restriction rules


We continue to close the feature parity gap between hosted XML and the inherited process model. This
new work item type rule lets you restrict work items from being moved from one state to another. For
example, you can restrict Bugs from going from New to Resolved. Instead, they must go from New –>
Active -> Resolved
You can also create a rule to restrict state transitions by group membership. For example, only users in
the “Approvers” group can move user stories from New -> Approved.

Copy work item to copy children


One of the top requested features for Azure Boards is the ability to copy a work item that also copies the
child work items. We added a new option to "Include child work items" to the copy work item dialog.
When selected, this option will copy the work item and copy all child work items (up to 100).

Improved rules for activated and resolved fields


Up until now, the rules for Activated By, Activated Date, Resolved By, and Resolved Date have been a
mystery. They are only set for system work item types and are specific to the state value of "Active" and
"Resolved". We've changed the logic so that these rules are no longer for a specific state. Instead, they
are triggered by the category (state category) that the state resides in. For example, let's say you have a
custom state of "Needs Testing" in the Resolved category. When the work item changes from "Active" to
"Needs Testing", the Resolved By and Resolved Date rules are triggered.
This allows customers to create any custom state values and still generate the Activated By, Activated
Date, Resolved By, and Resolved Date fields, without the need to use custom rules.

Stakeholders can move work items across board columns


Stakeholders have always been able to change the state of work items. But when they go to the Kanban
board, they're unable to move the work items from one column to another. Instead, Stakeholders would
have to open each work item, one at a time, and update the state value. This has long been a pain point
for customers, and we're happy to announce that you can now move work items across board columns.

System work item types on backlogs and boards


Now you can add a system work item type to the backlog level of choice. Historically these work item
types have only been available from queries.
Process Work Item Type
Agile Issue
Scrum Impediment
CMMI Change Request
Issue
Review
Risk
Adding a system work item type to a backlog level is simple. Just go into your custom process and
click the Backlog Levels tab. Select your backlog level of choice (example: Requirements Backlog)
and choose the edit option. Then add the work item type.

Audit logging event


We have added a new event to the audit logs to help customers better track process related changes.
An event will be logged whenever the values on a picklist are changed. Changes to picklist fields are
usually the most common changes made to a process. With this new event, collection admins can better
track when and who made changes to those fields.

Azure Boards GitHub app repo limit raised


The repo limit for the Azure Boards application in the GitHub marketplace has been increased from 100
to 250.

Customize work item state when pull request is merged


Not all workflows are the same. Some customers want to close out their related work items when a Pull
Request is completed. Others want to set the work items to another state to be validated before closing.
We should allow for both.
We have a new feature that allows you to set the work items to the desired state when the pull request
is merged and completed. To do this, we scan the pull request description and look for the state value
followed by the #mention of the work item(s). In this example, we are setting two user stories to
Resolved and closing two tasks.

Link your work item to builds in another project


You can now easily track your build dependencies across project just by linking your work item to a
Build, Found in build, or Integrated in build.

Editing description (help text) on system fields


You have always been able to edit the description of custom fields. But for system fields like priority,
severity, and activity, the description was not editable. This was a feature gap between the Hosted XML
and Inherited that prevented some customers from migrating to the Inherited model. You can now edit
the description on system fields. The edited value will only affect that field in the process and for that
work item type. This gives you the flexibility to have different descriptions for the same field on different
work item types.

Customize work item state when pull request is merged


Pull requests often refer to multiple work items. When you create or update a pull request, you may
want to close some of them, resolve some of them, and keep the rest open. You can now use comments
such as the ones shown in the figure below to accomplish that. See documentation for more details.

Parent field on the task board


Due to popular request, you can now add the Parent field to both the child and parent cards on the Task
Board.

Removing "Assigned To" rule on Bug work item type


There are several hidden system rules across all the different work item types in Agile, Scrum, and
CMMI. These rules have existed for over a decade and have generally worked fine without any
complaints. However, there are a couple of rules that have run out their welcome. One rule in particular
has caused a lot of pain for new and existing customers and we have decided it was time to remove it.
This rule exists on the Bug work item type in the Agile process.
"Set the Assigned value to Created By when state is changed to Resolved"
We received a lot of your feedback about this rule. In response, we went ahead and removed this rule
from the Bug work item type in the Agile process. This change will affect every project using an inherited
Agile or a customized inherited Agile process. For those customers who like and depend on this current
rule, please see our blog post on the steps you can take to re-add the rule in using custom rules.

Removed items on the Work Items page


The Work Items page is a great place to quickly find items you created or that are assigned to you,
amongst other things. It provides several personalized pivots and filters. One of the top complaints for
the "Assigned to me" pivot is that it displays Removed work i

Azure DevOps Server 完整介绍 1. 什么是Azure DevOps Server2. 内网部署和云端服务3. 技术架构3.1 服务器架构3.2 扩展和定制开发3.3 客户端4. 工作项管理5. 版本管理5.1 Team Foundation Version Control - TFVC5.2 Git6. 全文索引7. 流水线8. 测试管理9. 制品库Artifacts10. 版本路径1. 什么是Azure DevOps Se... 阅读详情

相关推荐

Azure DevOps Server 2019 (TFS)安装教程

概述Azure DevOps Server 2019 (之前的名称为TFS),作为微软Azure DevOps 的企业私有(on-premises)服务器,是一个为开发团队提供软件协作开发管理的服务平台,在需求管理、代码管理、持续集成和交付、敏捷开发方面为软件开发团队提供全流程的技术服务。这一运行在企业内网中的开发服务器,由于具备入门门槛低、成本费用低、功能齐全等特点,深受国内软件开发团队、管理...

Azure DevOps Server(原名TFS) 694

Azure DevOps Server (TFS)的产品生命周期

Azure DevOps Server (之前名称为TFS)是Azure DevOps 是微软公司的软件研发管理平台产品,作为一款应用软件,它和其他所有软件产品一样不可避免的存在功能不足、产品缺陷、安全漏洞等不可以预知的问题。产品中存在问题,就需要我们去修复它。微软会帮助你修复产品中的问题吗?你公司运行的产品是否在微软公司的支持范围内?回答这个问题,我们首先需要了解Azure DevOps Se...

Azure DevOps Server(原名TFS) 671

Azure DevOps Server 的安装教程

Azure DevOps Server 安装指南 下载链接:https://azure.microsoft.com/zh-cn/services/devops/server/ 1、安装好了会出现以下界面: 其实微软的产品,你就跟着下一步下一步就好了,没什么难度。 2、新部署 如果你是从 TFS 20xx 升级上来的,就选择已有部署。 3、部署类型 如果你不需要使用 SQL Reporting S...

不忘初心 1万+

Azure DevOps Server(TFS) 客户端分析

Azure DevOps Server(TFS) 是微软公司的软件协作开发管理平台产品,为软件研发、测试、实施提供全流程的服务。作为一款应用服务器产品,他的客户端是什么,在哪里下载客户端?我们在项目实施过程,经常碰到这样的问题。本文的目的就是为了解答这个问题。作为一款企业级的软件研发管理平台,Azure DevOps Server 集成了需求管理、项目计划、人员管理、代码管理、持续集成、自动发布...

Azure DevOps Server(原名TFS) 763

什么是Azure DevOps Server?

经常有朋友来咨询,是否有关于Azure DevOps Server 描述资料?首先我会把微软官方的文档(https://docs.microsoft.com/en-us/azure/devops)推荐给对方,因为官方文档库中几千页的文字描述是最权威且最完整的介绍了。但是还是有些朋友认为官方得文档比较倾向于操作说明,希望有一个比较概要性的说明文档。我把自己对Azure DevOps Server这...

Azure DevOps Server(原名TFS) 2255

Azure DevOps Server:使用TfsDeleteProject.exe删除团队项目

Contents1. 概述2. 使用方法1. 删除后不能恢复2. 获取TfsDeleteProject.exe3. 必要权限4. 操作说明5. 验证删除效果1. 概述Azure DevOps Server(原名TFS)是微软公司的研发管理平台产品,它使用团队项目(Team Project)作为管理数据的基本单元,团队项目中存储了开发团队的大量开发数据,包括需求、任务、迭代计划、源代码、持续集成和...

Azure DevOps Server(原名TFS) 1298

实测在 Microsoft Windows 11上使用Azure DevOps Server (TFS)

1. 概述 微软官方上周(20201/5/25)发布了Azure DevOps Server 2020.1的正式版本,在2020版本的基础上增加了大量最新功能( 2.

Azure DevOps Server(原名TFS) 927

部署Azure DevOps Server(TFS)的高可用节点(负载均衡)

1. 概述Azure DevOps Server (之前称TFS)是微软公司的软件研发管理平台产品,为研发团队提供需求、开发、测试和持续集成和交付的全流程服务。这个产品从设计之初,就综合考虑了兼容不同规模的研发团队,它支持小到3-5个人的团队,多到几万人的软件研发团队。对于大规模的软件研发团队,DevOps Server从应用层的扩展性和数据库层的高可用性方面,做了非常完善的设计。下图是一个比较...

Azure DevOps Server(原名TFS) 652

Azure DevOps Server 2019.pptx

Introducing Azure DevOps Server DevOps allows us to accelerate delivery, while still delivering reliable products and services

欧姆龙 CJ1W-SCU模块使用通配符+结束码实现非固定长度数据的接收

实验设备:CJ2M-CPU33、CJ1W-SCU21、XW2Z-200T 实验目的:了解 CJ1W-SCU 通配符使用 1.硬件接线: CJ1W-SCU21单元号拨码置于8,使用串口1(232口)。 2.软件设置: ① 新建工程,选择PLC型号CJ2M-CPU33,切换到编程模式,如下图: 、 ② 创建I/O并进行相关配置,如下图: ③ 设置为用户设置,协议宏模式,8位数据位,2位停止位,偶校验9600波特率,如下图: 、 ④ 打开CX-Protocal软件,新建工程: .

weixin_42118352的博客 1987

LightRAG实战:从零构建中药知识图谱,解锁六种检索模式效能对比

本文详细介绍了如何使用轻量级RAG框架LightRAG从零构建中药知识图谱的实战过程。通过本地部署环境搭建、开源模型配置与《本草纲目》数据导入,文章重点对比了Naive、Local、Global、Hybrid、Mix和Bypass六种检索模式在中药问答中的效能差异,并提供了可视化图谱与优化心得,为开发者构建专业领域智能问答系统提供了实用指南。

weixin_29096377的博客 178

INS/伪距组合导航(1)

星间单差GNSS/INS伪距紧组合

u014430081的博客 877

制作Ubuntu22.04启动盘

现在越来越多程序代码都需要运行在linux环境下,运行这些代码的前提是安装一个稳定的linux操作系统。本文选择Ubuntu 22.04去制作系统启动盘。本文主要对ubuntu22.04的启动盘制作过程进行了详细的说明,希望能帮助到有需要的朋友。

lyx_ok的博客 1万+

STM32硬件SPI驱动ADS1220实战:从零搭建高精度数据采集系统(附避坑指南)

本文详细介绍了使用STM32硬件SPI驱动24位高精度ADC芯片ADS1220的完整实战方案。内容涵盖从硬件设计、CubeMX工程配置、SPI通信底层实现到数据读取策略与性能优化的全流程,并重点分享了多通道切换、噪声抑制等关键避坑指南,帮助开发者构建稳定可靠的高精度数据采集系统。

o4p5q6r7s的博客 455

DDM-MIMO-FMCW雷达速度模糊与解模糊MATLAB仿真

本文深入解析了DDM-MIMO-FMCW雷达中的速度模糊现象及其解模糊方法,通过MATLAB仿真详细展示了相位编码解调、速度扩展算法和混合波形设计三大解决方案。文章还提供了参数配置、信号建模和结果可视化的实用技巧,并分享了工程实践中的避坑指南,帮助开发者高效解决雷达信号处理中的速度模糊问题。

weixin_31528001的博客 350

STM32开发 -- LIS3DH三轴加速度计开发详解

这次要讲一下LIS3DH三轴加速度计的开发使用,之前是有讲过 MPU6050开发 的,但当时是在Linux下做的。额,还是个半成品,哈哈。现在手边有STM32的开发板,可以实实在在的来实现以下卡尔曼滤波了。 一、LIS3DH初识 依照惯例,先看一下手册,大致先了解一下,LIS3DH是什么模块。 下载:LIS3DH datasheet 1、描述 LIS3DH是一款超低功耗高性能三轴线性加速度计,属于...

不积跬步,无以至千里 2万+

【25届数字IC秋招总结】面试经验10——紫光同芯

25届数字ic面试记录——紫光同芯

lalala0635的博客 865

LinePhone3.2.7(android端最新版本) sip客户端

SIP客户端For android:LinePhone3.2.7(最新版本),官网地址:http://www.linphone.org/

IDEA的使用指南

IDEA基于java的使用手册,可以最快速的上手,在使用中不断的丰富自己的使用技巧.

计算机控制技术及应用

《计算机控制技术及应用》通过总结作者的科研成果和吸收国内外的先进理论、方法和技术,以计算机控制系统的网络化、开放化、智能化和集成化发展趋势为主线索,主要介绍计算机控制系统的基本概念和计算机控制系统的典型形式,计算机控制系统的数学描述与基本分析方法,以及数字PID控制器、最少拍控制系统、达林算法、状态变量设计法等设计方法及其各种改进算法。重点突出计算机控制系统输入输出通道接口的设计方法和典型控制系统的设计案例与实现方法等。

NTscan扫描工具

ntscan是一个扫描器,可以扫描没有密码和弱密码的共享,先到配置文件中填写猜测的用户名和密码,扫描过程中右侧出现的是扫描日志。

上一篇: Azure DevOps Server 2020.1 升级指南 (TFS)
下一篇: Azure DevOps 通用包管理(Universal Artifacts)
Azure DevOps
博客等级 码龄6年 219粉丝 296原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值