In below image I can see that there are multiple tabs when we create pull request like Overview, Files, Update, Commits, etc. I want to add a new tab in pull request. I tried searching on internet but was not able to find much. It will be great if someone can help me with it.
Thank you
I agree with #4c74356b41 AFAIK that's not possible without creating a full-blown extension\addon.
Reference taken from :
Azure DevOps-Add extension that adds custom tab to Pipeline / Release Definition page (not the summary page) - Stack Overflow
. I don't know the term I should use to search for it.I am just not sure what to search in google to learn more about it.
you can search for the following terms on Google :
Azure DevOps extension samples
Azure DevOps extension custom tab
Azure Devops Extensions Overview
I am ok with adding addon\extension. I actually want to know some document references that can be useful in this scenario
As you are ok with extension you can refer this MS document Extensions overview.
To create a new tab in a pull request, you need to create an extension that adds the new functionality to Azure DevOps. You can use Visual Studio to create a new Azure DevOps extension project.
Reference for Working with Pull Requests in Visual Studio Code and Azure DevOps
Reference SO thread
Related
I have newly started exploring capabilities of Azure DevOps Wiki. I have multiple projects in Azure DevOps. I want to create one separate project to store Business & Technical documentation for all my projects in a centralize place. How can I add multiple Wiki pages to keep this organize.
Second question is I have a predefined structure for the documentation. For eg. Purpose Of Application, Local Build Steps, Deployment Steps, Third Party Control used, etc. How can I create & store this as a template so that whenever a new project documentation is to be created this document can be used as a placeholder to be followed by everyone.
How can I add multiple Wiki pages to keep this organize.
In Azure Devops, Wiki is similar to another kind of Repo. You could Clone Wiki to the target project and Publish the code as wiki.
Here are the steps:
Use the Clone wiki option to get the URL from other projects.
2.Navigate to the target project -> Repos. Use the import repositoryoption to import the wiki to the Repo.
Use the Publish Code as wiki option to publish the repo as wiki page.
Here is a doc about clone wiki.
How can I create & store this as a template?
Azure Devops doesn't support creating wiki templates now.
Here is a suggestion ticket about this feature. You could vote and add comments in this ticket.
Hope this helps.
I need to capture image form publish test result and that captured image needs to send in an email.
is this possible in Azure DevOps ci/cd pipeline?
I have attached below screenshot for reference.
Please help me.
This is not available as an out of the box feature as of today, AFAIK. At most, you can see the stats of the latest test run included in the build completion email notification with a link to the see them on the Portal.
However, you can search for suitable Azure DevOps extensions in the Visual Studio Marketplace, or submit your suggestion at the Developer Community for Azure DevOps for our Team to look at.
I am migrating from TFS 2015 to Azure DevOps. The process of creating the target project and importing the old git repository can easily be done through the Azure DevOps API.
But each new project, either created manually or by API has always all services (Boards, Pipelines, Test Lab, ...) enabled. Is there a way to change the default setting of which services should be enabled on new projects? Or even better an API method to switch certain services on / off?
We have hunderets of projects and therefor it's not feasible to open each project in the browser, change to the project settings page and adjust the services.
I haven't found anything in the docs: https://learn.microsoft.com/en-us/rest/api/azure/devops/?view=azure-devops-rest-5.0
This guy wrote a blog post on how to do this
This is an excerpt pulled from his post:
PATCH https://{account}.visualstudio.com/_apis/FeatureManagement/FeatureStates/host/project/{project-id}/{feature-id}?api-version='4.1-preview.1'
content-type: application/json
{"featureId":"{feature-id}","scope":{"settingScope":"project","userScoped":false},"state":0}
Replace account,project-id and feature-id as appropriate. Here are the feature id’s I know of.
ms.vss-build.pipelines [Azure Pipelines]
ms.vss-test-web.test [Test Plans]
ms.vss-work.agile [Azure Boards]
ms.vss-code.version-control [Azure Repos]
ms.feed.feed [Azure Artifacts]
It looks like turning a service off really just means hiding it from the UI.
Edit: it looks like the .net SDK has built in support for this as well
My company currently uses Jira and Confluence. In this setup, it is very easy to link a Jira ticket to a Confluence page, via a simple search inside the create link dialog.
We're now looking at moving to VSTS Work Items and Sharepoint. I'm wondering whether VSTS Work Items and Sharepoint are strongly integrated as well. Is it easy to insert a link in a VSTS Work Item to the latest version of a Sharepoint document?
The VSTS isn’t integrated with on-premise SharePoint, but you can add the link to the work item (Hyperlink type). So, they aren’t strongly integrated.
as workaround in Azure DevOps you can add a link to work item's description (enter to Description field, use icon "Create link" and paste this link to window which appears).
We are migrating our DocuSign Demo account to production. For this- we downloaded all templates from demo account as xml and uploaded same on production account- Which is working fine.
We have approx 200 custom Tabs created for these templates in demo account, is there any way to download/migrate these Custom Tabs to production account?
Good question, unfortunately there is no way of completely automating this; however there's one important thing I'll mention here which implies that you might not even have to migrate any of your Custom Tags, and I also have a manual workaround that will save you time if you do indeed want to migrate them.
First off, if you're using Custom Tags in templates only then you probably don't need to migrate any tags. The custom tag definition is embedded within the xml of your templates, so the system should have enough information to display and utilize them in your envelopes as expected.
However if you're using them in other places and/or you want them to show in the Custom Tag area of your production account preferences in order to modify them, then you can do the following to help save some time:
Create and save a template in demo that has all the Custom Tags that you want to migrate.
Migrate the template by downloading the template xml from demo and uploading into your production account.
Open the template and for each tab you want migrated double click and select Save As Custom. This will in turn add the Custom Tag to your production account.
Unfortunately that's the quickest way to migrate Custom Tags currently, but as mentioned you might not have to do this at all - your envelopes still have all the info they need to function properly in production.