Setting up Azure Dev Ops as a Source
Connecting Azure Work Items and Wiki makes it easy to bring your Azure DevOps content into Guru's knowledge ecosystem. Learn how to connect your Azure DevOps organization, manage permissions, and turn existing project information into trusted, searchable resources for generating Answers.
Access neededGuru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources.
Azure Dev Ops: You need to have Admin access in Azure Dev Ops to connect as a source.
Connecting Azure Dev Ops Work Items
- Go to Manage > Sources.
- Select Add Source.
- Choose Azure Dev Ops Work Items from the list of available integrations.
- Select My Credentials.
- Enter your Azure DevOps organization name:
- Sign in to your Azure DevOps account
- Go to Organizations
- Copy the organization name that appears after "dev.azure.com". For example, if you see "dev.azure.com/acme", enter acme
- Paste your organization name when prompted
- Add a display name for the Source (optional) and select Connect Source.
- Assign which Guru Groups should have access to this content.
Setting Up Azure Dev Ops Wiki
- Go to Manage > Sources.
- Select Add Source.
- Choose Azure Dev Ops Wiki from the list of available integrations.
- Name your source (optional).
- Use your credentials to sign into Azure Dev Ops Wiki.
- Select an account. This is set at the organization level in Azure Dev Ops wiki, so if you have multiple accounts you'd like to sync, you'll connect Azure Dev Ops Wiki multiple times.
- Select which wikis you want to sync into Guru.
- Add a display name for the Source (optional) and select Connect Source.
- Assign which Guru Groups should have access to this content.
Objects Synced From Azure Dev Ops
Azure Dev Ops Work Items
Primary objects are the objects used to generate the search record.
Common Model / What You'll See During Setup | Objects/Data Brought In | Key Fields |
---|---|---|
Ticket | Primary Objects: All work item types (Tasks, Bugs, User Stories, Features, Epics, etc.) | โข Name โข Description โข Ticket type โข Status (Enum) โข Priority (Enum) โข Due date โข Creator (UUID) โข Parent ticket (UUID) โข Project (Unknown) โข Ticket URL โข Completed at โข Remote created at โข Remote updated at โข Remote ID โข Remote data |
Tag | Tags/labels on work items | โข Name |
Attachment | File attachments on work items | โข File name โข File URL โข Ticket (UUID) โข Remote created at โข Remote ID โข Remote data |
Comment | Discussion comments on work items | โข Body โข HTML body โข User (UUID) โข Ticket (UUID) โข Remote created at โข Remote ID โข Remote data |
Project | Azure DevOps projects | โข Name โข Description โข Remote ID โข Remote data |
Collection | Project collections | โข Name โข Description โข Collection URL โข Remote created at โข Remote updated at โข Remote ID โข Remote data |
RemoteFieldClass | Custom field definitions | โข Display name โข Description โข Remote key name โข Item format โข Item type โข Is common model field (Boolean) โข Remote ID โข Remote data |
User | Project and team members | โข Name โข Email address โข Avatar โข Teams (Array) โข Remote ID โข Remote data |
Role | User roles/permissions | โข Name |
Team | Project teams | โข Name โข Description โข Remote ID โข Remote data |
Azure Dev Ops Wiki
- Provisioned Wikis that you select
- Code Wikis that you select
Permissions
- When you connect Azure Dev Ops Work Items or Wiki as a source in Guru, you'll permission that content in Guru. Learn more here.
- If someone is not provided with access in Guru to this source, they will not see Azure Dev Ops results in searches or when chatting with Guru.
Frequently Asked Questions
What if I have multiple Azure Dev Ops Wiki organizations?
The integration connects at the Azure DevOps Organization level. If you have multiple organizations, you'll need to connect them seperately.
What if I add a wiki to Azure Dev Ops after I initially sync it?**
You'll need to navigate back to Manage > Sources, to the source, then select Reauthorize
Updated 1 day ago