Azure-Devops-Extension：默认情况下，使所有进程的组贡献为可选
我目前正在开发一个 Azure DevOps 扩展，其中包含工作项的小组贡献：ms.vss-work-web.work-item-form-group。 不幸的是，我意识到这个贡献被添加到默认情况下安装扩展的组织的任何进程中。由于我们组织内有多个使用不同流程的不同项目，并且此扩展仅旨在在一个项目中使用，因此我正在寻找一种设置，使所有流程默认禁用此贡献（包括无法编辑的预定义流程）。我知道组集成可以手动隐藏在进程设置中的页面修改器中（对于继承的进程），但我希望手动添加此集成，而不是默认添加。此外，一些项目使用无法编辑的默认流程，因此据我所知无法删除组集成。不幸的是，我在文档中找不到任何相关内容。
I am currently developing an Azure Devops Extension with a group contribution for work items: ms.vss-work-web.work-item-form-group.
Unfortunately, I realized that this contribution is added to any Proccess of the organization the extension is installed to by default. Since we have multiple different projects using different processes within our organization, and this extension only aims to be used in one single project, I am looking for a setting that makes this contribution disabled by default for all processes (including the predefined processes which cannot be edited). I am aware that the group integration can be manually hidden in the page modifier in the process settings (for inherited processes) but I want this integration to be manually added and not added by default. Also some projects use the default processes which cannot be edited and therefore the group integration cannot be removed as far as I know. Unfortunately, I wasn't able to find anything about that in the documentation.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您无法在流程模板级别配置扩展。除了隐藏/显示贡献之外，就是这样。如果您使用的是基本模板，您也不能这样做。
但是，您可以使用功能标志来启用/禁用集合或项目级别的贡献。
您可以在 此处找到示例。
You can not configure extensions on process template level. Other than hiding/showing the contributions, that is. And if you are using base template, you can not do that, either.
However you could use feature flags for enabling/disabling contributions on collection or project level.
You can find an example here.